| Components | All | New | MacOS | Windows | Linux | iOS | ||||
| Examples | Mac & Win | Server | Client | Guides | Statistic | FMM | Blog | Deprecated | Old | |
CURL.SetOptionRange
Sets the range.
| Component | Version | macOS | Windows | Linux | Server | iOS SDK |
| CURL | 2.5 | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
MBS( "CURL.SetOptionRange"; curl; Value { ; Encoding } ) More
Parameters
| Parameter | Description | Example | Flags |
|---|---|---|---|
| curl | The CURL session handle. | $curl | |
| Value | Range string. | "1000-2000" | |
| Encoding | The text encoding for text parameter. Default is UTF-8. Possible encoding names: ANSI, ISO-8859-1, Latin1, Mac, Native, UTF-8, DOS, Hex, Base64 or Windows. More listed in the FAQ. |
"utf8" | Optional |
Result
Returns "OK" on success.
Description
Sets the range.Pass a text as parameter, which should contain the specified range you 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 "X-Y,N-M". Using this kind of multiple intervals will cause the HTTP server to send the response document in pieces (using standard MIME separation techniques). For RTSP, the formatting of a range should follow RFC 2326 Section 12.29. For RTSP, byte ranges are not permitted. Instead, ranges should be given in npt, utc, or smpte formats.
Pass an empty string to this option to disable the use of ranges.
Ranges work on HTTP, FTP, FILE (since 7.18.0), and RTSP (since 7.20.0) transfers only.
See also RANGE option in CURL manual.
Examples
Get the first 200 bytes:
Set Variable [$r; MBS( "CURL.SetOptionRange"; $curl; "0-199") ]
Set Variable [$r; MBS( "CURL.SetOptionURL; $curl; "https://example.com") ]
See also
- CURL.SetOptionNetRC
- CURL.SetOptionPort
- CURL.SetOptionPost
- CURL.SetOptionProxy
- CURL.SetOptionPut
- CURL.SetOptionQuote
- CURL.SetOptionReferer
- CURL.SetOptionResolve
- CURL.SetOptionSSLKey
- CURL.SetOptionURL
Blog Entries
Created 18th August 2014, last changed 6th September 2021
