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

DOCS: Added clarification to CURLOPT_CUSTOMREQUEST for the POP3 protocol

Browse Source 
Bug: http://curl.haxx.se/mail/lib-2012-06/0302.html
Reported by: Nagai H
This commit is contained in:
Steve Holme 2012-06-24 23:23:30 +01:00
parent a28cda3653
commit 1eb74f94c4
1 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/libcurl/curl_easy_setopt.3
View File

@ -1883,12 +1883,18 @@ something, you don't actually change how libcurl behaves or acts in regards
to the particular request method, it will only change the actual string sent to the particular request method, it will only change the actual string sent
in the request. in the request.
For example: if you tell libcurl to do a HEAD request, but then change the For example:
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 With the HTTP protocol when you tell libcurl to do a HEAD request, but then
POST, use \fICURLOPT_POST\fP or \fICURLOPT_POSTFIELDS\fP and so on. specify a GET though a custom request libcurl will still act as if it sent a
HEAD. 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 to switch
to a proper GET use CURLOPT_HTTPGET.
With the POP3 protocol when you tell libcurl to use a custom request it will
behave like a LIST or RETR command was sent where it expects data to be
returned by the server. As such \fICURLOPT_NOBODY\fP should be used when
specifing commands such as DELE and NOOP for example.
Restore to the internal default by setting this to NULL. Restore to the internal default by setting this to NULL.