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.

Author jhylton
Recipients
Date 2002-10-11.15:40:04
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=31392

I'm still uncertain about what to do on 301 responses.  As
you say, there are two issues to sort out: 1) what method
should a POST be redicted to and 2) whether the user should
be asked to confirm.

There's discussion of this at:
http://ppewww.ph.gla.ac.uk/~flavell/www/post-redirect.html
The page is a bit old, but I don't know if it is out of date.
It says that IE5, Netscape 4, and Mozilla 1.0 all redirect a
301 POST to a GET without user confirmation.  That seems
like a widespread disregard for the spec that we ought to
emulate.

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.

History
Date User Action Args
2007-08-23 14:01:00adminlinkissue549151 messages
2007-08-23 14:01:00admincreate