From c53fb36b0ce708c9418bdd9b44075f76f821dfcc Mon Sep 17 00:00:00 2001 From: Peter Gal Date: Fri, 7 Jun 2013 16:39:16 +0200 Subject: curl_easy_setopt.3: HTTP header with no content Update the documentation on how to specify a HTTP header with no content. --- docs/libcurl/curl_easy_setopt.3 | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'docs/libcurl') diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3 index 742f3a18a..3b804a1f6 100644 --- a/docs/libcurl/curl_easy_setopt.3 +++ b/docs/libcurl/curl_easy_setopt.3 @@ -1436,10 +1436,12 @@ internally, your added one will be used instead. If you add a header with no content as in 'Accept:' (no data on the right side of the colon), the internally used header will get disabled. Thus, using this option you can add new headers, replace internal headers and remove internal headers. To add a -header with no content, make the content be two quotes: \&"". The headers -included in the linked list must not be CRLF-terminated, because curl adds -CRLF after each header item. Failure to comply with this will result in -strange bugs because the server will most likely ignore part of the headers +header with no content (nothing to the right side of the colon), use the +form 'MyHeader;' (note the ending semicolon). + +The headers included in the linked list must not be CRLF-terminated, because +curl adds CRLF after each header item. Failure to comply with this will result +in strange bugs because the server will most likely ignore part of the headers you specified. The first line in a request (containing the method, usually a GET or POST) is -- cgit v1.2.3