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 jjlee
Recipients
Date 2002-10-15.15:22:42
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=261020

Well, when I carefully read the RFC I came to the conclusion
that 301 should be redirected to GET, not POST.  I also came
to the conclusion that the RFC was slightly ambiguous on
this point, so I guess that's why A. Flavell came to the
conclusion that 301 should redirect to POST rather than GET.
Anyway, clearly the established practice is to redirect 301
as GET, so this is all academic.

Assuming he's right about Netscape / IE etc., I suppose I'm
happy for 301 to redirect without an exception, since that's
what we've agreed to do for 302.  Obviously, the docs should
say this is contrary to the RFC (as my doc patch says for
302 already).

As for urllib.py, I see the problem.  303 should still be
added, though, since that poses no problem at all.


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