➜

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 andresriancho
Recipients andresriancho, facundobatista, orsenthil
Date 2007-11-08.17:56:10
SpamBayes Score 0.054891657
Marked as misclassified No
Message-id <[email protected]>
In-reply-to
Content 
According to the RFC:

If urllib2 gets a 302 in response to a request, it MUST send the *same*
request to the URI specified in the Location header, without modifying
the method, headers, or any data (urllib2 is not RFC compliant here)

In urllib2, a 301 and a 307 message should be handled just like a 302.

If urllib2 gets a 303 in response to a request, it MUST send a GET
request to the URI specified in the Location header (urllib2 is "half"
RFC compliant here, this only works if the original request WASN'T a
POST request)

I will code a complete patch to make urllib2 work as RFC Compliant as
possible. Whenever it's ready i'll send it.
History
Date User Action Args
2007-11-08 17:56:11andresrianchosetspambayes_score: 0.0548917 -> 0.054891657
recipients: + andresriancho, facundobatista, orsenthil
2007-11-08 17:56:11andresrianchosetspambayes_score: 0.0548917 -> 0.0548917
messageid: <[email protected]>
2007-11-08 17:56:11andresriancholinkissue1401 messages
2007-11-08 17:56:10andresrianchocreate