From: Jay Satiro Date: Fri, 18 Nov 2022 08:54:16 +0000 (-0500) Subject: CURLOPT_POST.3: Explain setting to 0 changes request type X-Git-Tag: curl-7_87_0~132 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=e08382a208d4e4809752701b08c6c64f8f9fbada;p=thirdparty%2Fcurl.git 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 --- diff --git a/docs/libcurl/opts/CURLOPT_POST.3 b/docs/libcurl/opts/CURLOPT_POST.3 index a1a7eae444..f93e18786f 100644 --- a/docs/libcurl/opts/CURLOPT_POST.3 +++ b/docs/libcurl/opts/CURLOPT_POST.3 @@ -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 re-used handle, you must explicitly set the new request type using \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 0, disabled .SH PROTOCOLS