mirror of
https://github.com/curl/curl.git
synced 2025-01-24 14:15:18 +08:00
docs: fix man page syntax to make test 1140 OK again
This commit is contained in:
parent
af32cd3859
commit
96186de1f7
@ -48,13 +48,13 @@ specific backend at first use. If no selection is done by the program using
|
||||
libcurl, this variable's selection will be used. It should be set to the full
|
||||
SSL backend name to use (case insensitve).
|
||||
.IP HOME
|
||||
When the netrc feature is used (\fBCURLOPT_NETRC(3)\fP), this variable is
|
||||
When the netrc feature is used (\fICURLOPT_NETRC(3)\fP), this variable is
|
||||
checked as the primary way to find the "current" home directory in which
|
||||
the .netrc file is likely to exist.
|
||||
.IP LOGNAME
|
||||
User name to use when invoking the ntlm-wb tool, if NTLMUSER wasn't set.
|
||||
.IP NO_PROXY
|
||||
This has the same functionality as the \fBCURLOPT_NOPROXY(3)\fP option: it
|
||||
This has the same functionality as the \fICURLOPT_NOPROXY(3)\fP option: it
|
||||
gives libcurl a comma-separated list of host name patterns for which libcurl
|
||||
should not use a proxy.
|
||||
.IP NTLMUSER
|
||||
|
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user