On Mon, 15 Apr 2002, Dirk Manske wrote:

> > | Note: When automatically redirecting a POST request after
> > | receiving a 301 status code, some existing HTTP/1.0 user agents
> > | will erroneously change it into a GET request.
> >
> > Hmm, libcurl is right...but most browsers do a get after a 301 to follow.
>
> Here comes a better patch, forget previously sent patch:

[snip]

Do the browsers do that check-for-? logic or how come you introduced that?

I really don't like this patch, but if the browsers do like this then we're
kind of forced to break the RFC too, even though we do right now.

What concerns me here is also that adding this fix might in fact introduce a
reversed problem in the future when "the others" may decide to follow the
standards...

Anyone else with opinions on this matter?

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/