mirror of
https://github.com/moparisthebest/curl
synced 2024-12-23 00:28:48 -05:00
CURLOPT_HEADERFUNCTION: works for non-HTTP protocols too
This commit is contained in:
parent
77bac26587
commit
3ebcfdda36
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user