-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ClientResponse().history elements to ClientResponseError #1741
Comments
Let's just add history to exception. Do we really need new type? |
Just following request_info idea. |
|
Accepted. Thank you! |
Merged |
Long story short
During investigation of HTTP client exceptions on big installations, history can provide information about failure reason (incorrect redirect and etc).
De-facto needed fields:
url, code, reason, location if present in headers (all headers is better)
Expected behaviour
Accessible list
ClientResponseError().history
Actual behaviour
Currently this information is unavailable.
Proposed solution:
The text was updated successfully, but these errors were encountered: