Hello,
I've noticed that the documentation on how to specify a HTTP header
without content, does not contains the usage of semicolon.
See the attached patch. Hope it is ok.
Regards,
Peter
>From 15318bbb526bf70ea587e4dfabec8e209cb3b2b8 Mon Sep 17 00:00:00 2001
From: Peter Gal <[email protected]>
Date: Fri, 7 Jun 2013 16:39:16 +0200
Subject: [PATCH] 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 | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3
index 742f3a1..5ac69bc 100644
--- a/docs/libcurl/curl_easy_setopt.3
+++ b/docs/libcurl/curl_easy_setopt.3
@@ -1436,10 +1436,10 @@ 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, 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
--
1.8.3
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
