From: Daniel Stenberg <daniel@haxx.se>
Date: Wed, 9 Jun 2004 08:05:23 +0000 (+0000)
Subject: Setting CURLOPT_RANGE to NULL disables it.
X-Git-Tag: curl-7_12_1~306
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=b3caf7bfa85462b8b3653fc70e732f6b16cc2a38;p=thirdparty%2Fcurl.git

Setting CURLOPT_RANGE to NULL disables it.
Setting CURLOPT_RESUME_FROM to 0 prevents a resumed transfer.
---

diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3
index 095c1d7b59..94b5626d03 100644
--- a/docs/libcurl/curl_easy_setopt.3
+++ b/docs/libcurl/curl_easy_setopt.3
@@ -695,10 +695,11 @@ want. It should be in the format "X-Y", where X or Y may be left out. HTTP
 transfers also support several intervals, separated with commas as in
 \fI"X-Y,N-M"\fP. Using this kind of multiple intervals will cause the HTTP
 server to send the response document in pieces (using standard MIME separation
-techniques).
+techniques). Pass a NULL to this option to disable the use of ranges.
 .IP CURLOPT_RESUME_FROM
 Pass a long as parameter. It contains the offset in number of bytes that you
-want the transfer to start from.
+want the transfer to start from. Set this option to 0 to make the transfer
+start from the beginning (effectively disabling resume).
 .IP CURLOPT_RESUME_FROM_LARGE
 Pass an curl_off_t as parameter. It contains the offset in number of bytes
 that you want the transfer to start from. (Added in 7.11.0)