Previous requests in redirect chain don't track their history #1929

Closed
alex opened this Issue Feb 25, 2014 · 3 comments

Projects

None yet

5 participants

@alex
Contributor
alex commented Feb 25, 2014

Example:

>>> response = requests.get("http://djangoproject.com")
>>> response.history
(<Response [301]>, <Response [301]>)
>>> response.history[0].history
[]
>>> response.history[1].history
[]

I would have expected the first of the two items in history to have a history of its own.

@Lukasa
Collaborator
Lukasa commented Feb 25, 2014

Thanks for this @alex! Assuming #1919 gets cleaned up this should be fixed by that pull request. =)

@zackw
Contributor
zackw commented Feb 26, 2014

I'm actually thinking it'll be better to do stuff in a different order, see pull request #1930, but yeah, this is definitely on my todo list.

@ContinuousFunction ContinuousFunction added a commit to ContinuousFunction/requests that referenced this issue Aug 18, 2014
@ContinuousFunction ContinuousFunction Tracking Previous Requests
Addresses the issue brought up here:
kennethreitz#1929
df641e7
@kennethreitz
Owner

@alex fixed!

@willingc willingc added a commit to willingc/requests that referenced this issue Aug 27, 2014
@ContinuousFunction ContinuousFunction Tracking Previous Requests
Addresses the issue brought up here:
kennethreitz#1929
02df28d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment