generic-library/curl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

further clarifcation based on input from Anthony Bryan

Browse Source
This commit is contained in:
Daniel Stenberg
2008-12-29 21:26:11 +00:00
parent 59227bf075
commit 9aea3e265d
2 changed files with 18 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
docs/libcurl/curl_easy_setopt.3
View File

@@ -607,12 +607,9 @@ the authentication method.
Pass a char * as parameter, which should be pointing to the zero terminated Pass a char * as parameter, which should be pointing to the zero terminated
user name to use for the transfer. user name to use for the transfer.
The CURLOPT_USERNAME option should be used in the same way that \fBCURLOPT_USERNAME\fP sets the user name to be used in protocol
\fICURLOPT_USERPWD\fP is used. In comparison to \fICURLOPT_USERPWD\fP the authentication. You should not use this option together with the (older)
CURLOPT_USERNAME allows the username to contain a colon, like in the following CURLOPT_USERPWD option.
example: "sip:user@example.com". Note the CURLOPT_USERNAME option is an
alternative way to set the user name. There is no meaning to use it together
with the \fICURLOPT_USERPWD\fP option.
In order to specify the password to be used in conjunction with the user name In order to specify the password to be used in conjunction with the user name
use the \fICURLOPT_PASSWORD\fP option. (Added in 7.19.1) use the \fICURLOPT_PASSWORD\fP option. (Added in 7.19.1)
@@ -1212,12 +1209,17 @@ when doing a FTP directory listing. This is useful for doing DELETE or other
more or less obscure HTTP requests. Don't do this at will, make sure your more or less obscure HTTP requests. Don't do this at will, make sure your
server supports the command first. server supports the command first.
Note that libcurl will still act and assume the keyword it would use if you When you change the request method by setting \fBCURLOPT_CUSTOMREQUEST\fP to
didn't set your custom one is the one in use and it will act according to something, you don't actually change how libcurl behaves or acts in regards to
that. Thus, changing this to a HEAD when libcurl otherwise would do a GET the particular request method, it will only change the actual string sent in
might cause libcurl to act funny, and similar. To switch to a proper HEAD, use the request.
\fICURLOPT_NOBODY\fP, to switch to a proper POST, use \fICURLOPT_POST\fP or
\fICURLOPT_POSTFIELDS\fP and so on. For example: if you tell libcurl to do a HEAD request, but then change the
request to a "GET" with \fBCURLOPT_CUSTOMREQUEST\fP you'll still see libcurl
act as if it sent a HEAD even when it does send a GET.
To switch to a proper HEAD, use \fICURLOPT_NOBODY\fP, to switch to a proper
POST, use \fICURLOPT_POST\fP or \fICURLOPT_POSTFIELDS\fP and so on.
Restore to the internal default by setting this to NULL. Restore to the internal default by setting this to NULL.

8
docs/libcurl/libcurl-tutorial.3
View File

@@ -987,11 +987,11 @@ in memory and used properly in subsequent requests when the same handle is
used. Many times this is enough, and you may not have to save the cookies to used. Many times this is enough, and you may not have to save the cookies to
disk at all. Note that the file you specify to CURLOPT_COOKIEFILE doesn't have disk at all. Note that the file you specify to CURLOPT_COOKIEFILE doesn't have
to exist to enable the parser, so a common way to just enable the parser and to exist to enable the parser, so a common way to just enable the parser and
not read any cookies is to use a the name of a file you know doesn't exist. not read any cookies is to use the name of a file you know doesn't exist.
If you would rather use existing cookies that you've previously received with your If you would rather use existing cookies that you've previously received with
Netscape or Mozilla browsers, you can make libcurl use that cookie file as your Netscape or Mozilla browsers, you can make libcurl use that cookie file
input. The CURLOPT_COOKIEFILE is used for that too, as libcurl will as input. The CURLOPT_COOKIEFILE is used for that too, as libcurl will
automatically find out what kind of file it is and act accordingly. automatically find out what kind of file it is and act accordingly.
Perhaps the most advanced cookie operation libcurl offers, is saving the Perhaps the most advanced cookie operation libcurl offers, is saving the