aboutsummaryrefslogtreecommitdiff
path: root/docs/libcurl/opts/CURLOPT_HTTPHEADER.3
diff options
context:
space:
mode:
Diffstat (limited to 'docs/libcurl/opts/CURLOPT_HTTPHEADER.3')
-rw-r--r--docs/libcurl/opts/CURLOPT_HTTPHEADER.34
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/libcurl/opts/CURLOPT_HTTPHEADER.3 b/docs/libcurl/opts/CURLOPT_HTTPHEADER.3
index c9f29e393..bc070915d 100644
--- a/docs/libcurl/opts/CURLOPT_HTTPHEADER.3
+++ b/docs/libcurl/opts/CURLOPT_HTTPHEADER.3
@@ -80,13 +80,13 @@ intend them to get sent.
Custom headers are sent in all requests done by the easy handles, which
implies that if you tell libcurl to follow redirects
-(\fBCURLOPT_FOLLOWLOCATION(3)\fP), the same set of custom headers will be sent
+(\fICURLOPT_FOLLOWLOCATION(3)\fP), the same set of custom headers will be sent
in the subsequent request. Redirects can of course go to other hosts and thus
those servers will get all the contents of your custom headers too.
Starting in 7.58.0, libcurl will specifically prevent "Authorization:" headers
from being sent to other hosts than the first used one, unless specifically
-permitted with the \fBCURLOPT_UNRESTRICTED_AUTH(3)\fP option.
+permitted with the \fICURLOPT_UNRESTRICTED_AUTH(3)\fP option.
.SH DEFAULT
NULL
.SH PROTOCOLS