Am Montag, 15. April 2002 17:06 schrieb Daniel Stenberg:
> 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 was too lazy to check if browsers use such a logic. So this logic is a
invention by me. (Not patented yet...)

> 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.
Yes, I hate..rrr..dislike it too. But we are not in a perfect world...

> 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...
May be we should to add a new flag "CURL_BE_UGLY_AS_BROWERS". :-(

.
DM
Received on 2002-04-15