On Fri, 16 Feb 2018, Guido Berhoerster wrote:
Then the callback does not get a complete header and it's up to the libcurl consumer to merge it with the previous header. Which is fine, since one usually needs to do other normalization as well, it's just not obvious from the documentation.
Thanks. Then how about adding the following section to the CURLOPT_HEADERFUNCTION man page to clafify?
LIMITATIONS libcurl does not unfold HTTP "folded headers" (deprecated since RFC 7230). A folder header is a header that continues on a subsequent line and starts with a whitespace. Such folds will be passed to the header callback as a separate one, although strictly it is just a continuation of the previous line. -- / daniel.haxx.se ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
