From: Daniel Stenberg Date: Sat, 24 May 2008 11:19:51 +0000 (+0000) Subject: Nikolai Kondrashov provided a clarification for CURLOPT_HEADERFUNCTION X-Git-Tag: curl-7_18_2~29 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2045c79e3745107badb5917d084ecd2913bef20b;p=thirdparty%2Fcurl.git Nikolai Kondrashov provided a clarification for CURLOPT_HEADERFUNCTION --- diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3 index 81dac8d577..d378edb4d2 100644 --- a/docs/libcurl/curl_easy_setopt.3 +++ b/docs/libcurl/curl_easy_setopt.3 @@ -270,6 +270,12 @@ of bytes actually taken care of, or return -1 to signal error to the library (it will cause it to abort the transfer with a \fICURLE_WRITE_ERROR\fP return code). +If this option is not set, or if it is set to NULL, but +\fICURLOPT_HEADERDATA\fP (\fICURLOPT_WRITEHEADER\fP) is set to anything but +NULL, the function used to accept response data will be used instead. That is, +it will be the function specified with \fICURLOPT_WRITEFUNCTION\fP, or if it +is not specified or NULL - the default, stream-writing function. + Since 7.14.1: When a server sends a chunked encoded transfer, it may contain a trailer. That trailer is identical to a HTTP header and if such a trailer is received it is passed to the application using this callback as well. There