CURLOPT_POST.3: Explain setting to 0 changes request type
Bug: https://github.com/curl/curl/issues/9849 Reported-by: MonkeybreadSoftware@users.noreply.github.com Closes https://github.com/curl/curl/pull/9942
This commit is contained in:
parent
8a6a48957f
commit
e08382a208
@ -68,6 +68,10 @@ When setting \fICURLOPT_POST(3)\fP to 1, libcurl will automatically set
|
|||||||
If you issue a POST request and then want to make a HEAD or GET using the same
|
If you issue a POST request and then want to make a HEAD or GET using the same
|
||||||
re-used handle, you must explicitly set the new request type using
|
re-used handle, you must explicitly set the new request type using
|
||||||
\fICURLOPT_NOBODY(3)\fP or \fICURLOPT_HTTPGET(3)\fP or similar.
|
\fICURLOPT_NOBODY(3)\fP or \fICURLOPT_HTTPGET(3)\fP or similar.
|
||||||
|
|
||||||
|
When setting \fICURLOPT_POST(3)\fP to 0, libcurl resets the request type to
|
||||||
|
the default to disable the POST. Typically that would mean it's reset to GET.
|
||||||
|
Instead you should set a new request type explicitly as described above.
|
||||||
.SH DEFAULT
|
.SH DEFAULT
|
||||||
0, disabled
|
0, disabled
|
||||||
.SH PROTOCOLS
|
.SH PROTOCOLS
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user