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 crustymonkey
Recipients crustymonkey, eric.araujo, orsenthil
Date 2012-03-02.19:18:53
SpamBayes Score 0.00011160701
Marked as misclassified No
Message-id <1330715934.87.0.231080083892.issue14144@psf.upfronthosting.co.za>
In-reply-to
Content
Senthil,

The HTTPRedirectHandler is already breaking RFC2616 by it's own admission in the code comments (from the source):

# Strictly (according to RFC 2616), 301 or 302 in response
# to a POST MUST NOT cause a redirection without confirmation
# from the user (of urllib2, in this case).  In practice,
# essentially all clients do redirect in this case, so we
# do the same.
# be conciliant with URIs containing a space

I can definitely understand the issue with changing the default behavior to redirect the POST data.  However, an added option which leaves the current behavior as the default shouldn't hurt.  I'm submitting a new patch file (urllib2.py.redirect_option.patch), which will do exactly that.
History
Date User Action Args
2012-03-02 19:18:54crustymonkeysetrecipients: + crustymonkey, orsenthil, eric.araujo
2012-03-02 19:18:54crustymonkeysetmessageid: <1330715934.87.0.231080083892.issue14144@psf.upfronthosting.co.za>
2012-03-02 19:18:54crustymonkeylinkissue14144 messages
2012-03-02 19:18:54crustymonkeycreate