Logged In: YES
user_id=261020
Agreement seems to have been reached on this in the
discussion of bug #549151. There is a patch there, but only
the change to the 303 case should be applied, not 301. The
docs need to state that 303 is automatically handled, too.
Jeremy Hylton, from bug #549151:
> 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.
John Lee, in reply:
> As for urllib.py, I see the problem. 303 should still be
> added, though, since that poses no problem at all.
John
|