On Tue, Jun 11, 2024 at 04:40:02PM +0200, Daniel Stenberg wrote: > 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?
That’s what I saw with HTTP, as expected, like callback "headerCRLF" callback "headerCRLF" callback "headerCRLF" callback "CRLF" But with file, it was callback "headerCRLF" callback "headerCRLF" callback "headerCRLFCRLF" -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
