Just wanted to chime in with a couple thoughts:

1) I think that's what the recent patch is for, but just to reiterate:
if 100/Continue behavior isn't supported by HTTP/1.1, then it should be
turned off by default. I did notice this behavior myself a while ago
in testing actually, that when I changed to HTTP/1.0 I still got the
100/Continue behavior.
2) As for documentation, I *live* in curl_easy_setopt, as it feels that
it's the place to fine-tune all behavior. Maybe a mention there? Or
maybe a new manual section on "protocols"? IE, curl_http, curl_ftp etc
where you can explain protocol-specific things?
3) I would like to note that a quick look through the available
curl_easy_setopt doesn't really contraindicate the addition of a
specific curl-opt for turning of HTTP/Continue behavior, so I can see
why Roman suggested it.

Regards,
Alan

On Aug 23, 2004, at 9:21 AM, Daniel Stenberg wrote:

> On Mon, 23 Aug 2004, Roman Koifman wrote:
>
>> By "practical" I mean that this possibility will be obvious from the
>> curl manual and not only from the code and the sniffer.
>
> Then I suggest we instead document the current behaviour properly. Any
> idea on where it should be written? Where would you look for this
> info?
>
> --
> Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
> Dedicated custom curl help for hire: http://haxx.se/curl.html
Received on 2004-08-23