From 34e5ad21d2cb98475acdbf7a3a6ea973d8c12249 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 27 Jul 2020 23:59:00 +0200 Subject: [PATCH] CURLOPT_NOBODY.3: fix the syntax for referring to options As test 1140 fails otherwise! Follow-up to e1bac81cc815 --- docs/libcurl/opts/CURLOPT_NOBODY.3 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/libcurl/opts/CURLOPT_NOBODY.3 b/docs/libcurl/opts/CURLOPT_NOBODY.3 index c6c23752b..3b2e393a1 100644 --- a/docs/libcurl/opts/CURLOPT_NOBODY.3 +++ b/docs/libcurl/opts/CURLOPT_NOBODY.3 @@ -33,13 +33,13 @@ output when doing what would otherwise be a download. For HTTP(S), this makes libcurl do a HEAD request. For most other protocols it means just not asking to transfer the body data. -For HTTP operations when \fBCURLOPT_NOBODY(3)\fP has been set, unsetting the +For HTTP operations when \fICURLOPT_NOBODY(3)\fP has been set, unsetting the option (with 0) will make it a GET again - only if the method is still set to be HEAD. The proper way to get back to a GET request is to set -\fBCURLOPT_HTTPGET(3)\fP and for other methods, use the POST ur UPLOAD +\fICURLOPT_HTTPGET(3)\fP and for other methods, use the POST ur UPLOAD options. -Enabling \fBCURLOPT_NOBODY(3)\fP means asking for a download without a body. +Enabling \fICURLOPT_NOBODY(3)\fP means asking for a download without a body. If you do a transfer with HTTP that involves a method other than HEAD, you will get a body (unless the resource and server sends a zero byte body for the