From 3ebcfdda36afeec0119c7f4f3fd8a37c5f9b37eb Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 7 May 2012 00:13:46 +0200 Subject: [PATCH] CURLOPT_HEADERFUNCTION: works for non-HTTP protocols too --- docs/libcurl/curl_easy_setopt.3 | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3 index 7d422e82a..830c1dd09 100644 --- a/docs/libcurl/curl_easy_setopt.3 +++ b/docs/libcurl/curl_easy_setopt.3 @@ -357,7 +357,7 @@ of bytes actually taken care of. If that amount differs from the amount passed to your function, it'll signal an error to the library. This will abort the transfer and return \fICURL_WRITE_ERROR\fP. -A complete header that is passed to this function can be up to +A complete HTTP header that is passed to this function can be up to \fICURL_MAX_HTTP_HEADER\fP (100K) bytes. If this option is not set, or if it is set to NULL, but @@ -380,6 +380,9 @@ to detect it being a trailer and not an ordinary header: 1) it comes after the response-body. 2) it comes after the final header line (CR LF) 3) a Trailer: header among the regular response-headers mention what header(s) to expect in the trailer. + +For non-HTTP protocols like FTP, POP3, IMAP and SMTP this function will get +called with the server responses to the commands that libcurl sends. .IP CURLOPT_WRITEHEADER (This option is also known as \fBCURLOPT_HEADERDATA\fP) Pass a pointer to be used to write the header part of the received data to. If you don't use