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: consistency in received headers
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Tue, 11 Jun 2024 16:40:02 +0200 (CEST)
On Tue, 11 Jun 2024, dogma via curl-library wrote:
> When receiving HTTP, the header callback is called at the end with just a
> CRLF, as specified in CURLOPT_HEADERFUNCTION(3).
>
> But for a file, the ending CRLF comes attached to the Last-Modified header
> (if there’s a body). I find it unexpected to be fed a header with two CRLFs.
I don't understand.
The headers are separated from the body with a stand-alone CRLF and that is
sent as a final header to the callback, is that what you mean?
Date: Tue, 11 Jun 2024 16:40:02 +0200 (CEST)
On Tue, 11 Jun 2024, dogma via curl-library wrote:
> When receiving HTTP, the header callback is called at the end with just a
> CRLF, as specified in CURLOPT_HEADERFUNCTION(3).
>
> But for a file, the ending CRLF comes attached to the Last-Modified header
> (if there’s a body). I find it unexpected to be fed a header with two CRLFs.
I don't understand.
The headers are separated from the body with a stand-alone CRLF and that is
sent as a final header to the callback, is that what you mean?
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2024-06-11