This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: urllib needs 303/307 handlers
Type: Stage:
Components: Library (Lib) Versions:
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: gvanrossum, jjlee
Priority: normal Keywords:

Created on 2002-06-12 15:36 by gvanrossum, last changed 2022-04-10 16:05 by admin. This issue is now closed.

Messages (3)
msg11174 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2002-06-12 15:36
See

http://mail.python.org/pipermail/python-dev/2002-June/025289.htm

and

http://ppewww.ph.gla.ac.uk/~flavell/www/post-redirect.html

There is also an issue with the 302 handler (also
discussed there).
msg11175 - (view) Author: John J Lee (jjlee) Date: 2002-10-21 20:42
Logged In: YES 
user_id=261020

Agreement seems to have been reached on this in the
discussion of bug #549151.  There is a patch there, but only
the change to the 303 case should be applied, not 301.  The
docs need to state that 303 is automatically handled, too.

Jeremy Hylton, from bug #549151:
> I agree with your interpretation that urllib2 raise an
> HTTPError to signal "request confirm" because an HTTPError
> is also a valid response that the user could interpret.
> But of urllib, an HTTP error doesn't contain a valid
> response.  The change would make it impossible for the
> client to do anything if a 301 response is returned from a
> POST.  That seems worse than doing the wrong.

John Lee, in reply:
> As for urllib.py, I see the problem.  303 should still be
> added, though, since that poses no problem at all.


John
msg11176 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2003-04-17 18:08
Logged In: YES 
user_id=6380

Deferring to discussion for patch 549151.
History
Date User Action Args
2022-04-10 16:05:24adminsetgithub: 36736
2002-06-12 15:36:25gvanrossumcreate