Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
Re: Strange behavior of Expect 100 Continue
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Ray Satiro via curl-library <curl-library_at_lists.haxx.se>
Date: Sun, 9 Mar 2025 18:21:30 -0400
On 2/6/2025 5:30 AM, Daniel Stenberg via curl-library wrote:
> On Mon, 3 Feb 2025, [Quipsy] Markus Karg via curl-library wrote:
>
>> The application is using curl easy API to create a curl instance,
>> sends a request, closes the instances, then does the same again, etc.
>> - which is working PRETTY WELL but rather slow.
>>
>> In an attempt to speed up things we wanted to reuse the existing
>> http/1.1 connection, so we removed the closing and reinitializing of
>> curl between each http invocation.
>>
>> But now the second invocation gets "100 Continue" response instead of
>> "200 OK"...?!
>
> From a libcurl point of view it makes the same identical HTTP request
> wether the connection is reused or fresh. It should not change the
> server behavior as to a 100 is returned or not. I would expect it to
> come or not come independent of connection reuse.
>
> I think this implies a bug somewhere.
Markus did you ever determine whether your application was the cause of
the problem? If you think there is a bug in curl then please try the
latest version [1] and if if the problem is still present then can you
open an issue [2] and include instructions that we can use to reproduce?
Thanks
[1]: https://curl.se/download.html
[2]: https://github.com/curl/curl/issues/new?template=bug_report.yml
Date: Sun, 9 Mar 2025 18:21:30 -0400
On 2/6/2025 5:30 AM, Daniel Stenberg via curl-library wrote:
> On Mon, 3 Feb 2025, [Quipsy] Markus Karg via curl-library wrote:
>
>> The application is using curl easy API to create a curl instance,
>> sends a request, closes the instances, then does the same again, etc.
>> - which is working PRETTY WELL but rather slow.
>>
>> In an attempt to speed up things we wanted to reuse the existing
>> http/1.1 connection, so we removed the closing and reinitializing of
>> curl between each http invocation.
>>
>> But now the second invocation gets "100 Continue" response instead of
>> "200 OK"...?!
>
> From a libcurl point of view it makes the same identical HTTP request
> wether the connection is reused or fresh. It should not change the
> server behavior as to a 100 is returned or not. I would expect it to
> come or not come independent of connection reuse.
>
> I think this implies a bug somewhere.
Markus did you ever determine whether your application was the cause of
the problem? If you think there is a bug in curl then please try the
latest version [1] and if if the problem is still present then can you
open an issue [2] and include instructions that we can use to reproduce?
Thanks
[1]: https://curl.se/download.html
[2]: https://github.com/curl/curl/issues/new?template=bug_report.yml
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2025-03-09