Skip to content

Conversation

@rshatch
Copy link

@rshatch rshatch commented Dec 6, 2019

When TooManyRedirects is raised, we already have some responses (1 + max_redirects)
We should return what we have along with the error message.

-Add response attribute to TooManyRedirects exception
-Add the existing response chain when we raise this exception
-Add tests to ensure the response + history we're returning is correct.

When TooManyRedirects is raised, we already have some responses (1 + max_redirects)
We should return what we have along with the error message.

-Add response attribute to TooManyRedirects exception
-Add the existing response chain when we raise this exception
-Add tests to ensure the response + history we're returning is correct.
@rshatch
Copy link
Author

rshatch commented Dec 6, 2019

This mimics behavior in Requests - I'm pretty sure I'm understanding the history stack right, but feel free to tweak it if I'm not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant