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 pitrou
Recipients andresriancho, facundobatista, jimjjewett, orsenthil, pitrou
Date 2008-01-17.20:24:28
SpamBayes Score 0.21128571
Marked as misclassified No
Message-id <>

Sending a 302 in response to a POST is a very common practice so that
the browser is redirected to a "normal", non state-changing page after
the POST request has been processed. It is useful in that it allows the
user to reload the resulting page (fetched with GET) without it popping
up a warning dialog, and without re-submitting the request if the user
validates the dialog.

So, a 302 response after a POST should generate a GET to the new URL.
And, of course, without a Content-Length (there's no content in a GET so
it can't have a length, does it?).
Date User Action Args
2008-01-17 20:24:30pitrousetspambayes_score: 0.211286 -> 0.21128571
recipients: + pitrou, facundobatista, jimjjewett, orsenthil, andresriancho
2008-01-17 20:24:30pitrousetspambayes_score: 0.211286 -> 0.211286
messageid: <>
2008-01-17 20:24:28pitroulinkissue1401 messages
2008-01-17 20:24:28pitroucreate