67211e9540
Remove use of .TP and some .B. The idea is to reduce nroff syntax as much as possible and to use it consistently. Ultimately, we should be able to introduce our own easier-to-use-and-read syntax/formatting and convert on generation time. Closes #12535
45 lines
1.5 KiB
Makefile
45 lines
1.5 KiB
Makefile
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
SPDX-License-Identifier: curl
|
|
Long: range
|
|
Short: r
|
|
Help: Retrieve only the bytes within RANGE
|
|
Arg: <range>
|
|
Protocols: HTTP FTP SFTP FILE
|
|
Category: http ftp sftp file
|
|
Example: --range 22-44 $URL
|
|
Added: 4.0
|
|
See-also: continue-at append
|
|
Multi: single
|
|
---
|
|
Retrieve a byte range (i.e. a partial document) from an HTTP/1.1, FTP or SFTP
|
|
server or a local FILE. Ranges can be specified in a number of ways.
|
|
.RS
|
|
.IP 0-499
|
|
specifies the first 500 bytes
|
|
.IP 500-999
|
|
specifies the second 500 bytes
|
|
.IP -500
|
|
specifies the last 500 bytes
|
|
.IP 9500-
|
|
specifies the bytes from offset 9500 and forward
|
|
.IP 0-0,-1
|
|
specifies the first and last byte only(*)(HTTP)
|
|
.IP 100-199,500-599
|
|
specifies two separate 100-byte ranges(*) (HTTP)
|
|
.RE
|
|
.IP
|
|
(*) = NOTE that this causes the server to reply with a multipart response,
|
|
which is returned as-is by curl! Parsing or otherwise transforming this
|
|
response is the responsibility of the caller.
|
|
|
|
Only digit characters (0-9) are valid in the 'start' and 'stop' fields of the
|
|
'start-stop' range syntax. If a non-digit character is given in the range, the
|
|
server's response is unspecified, depending on the server's configuration.
|
|
|
|
Many HTTP/1.1 servers do not have this feature enabled, so that when you
|
|
attempt to get a range, curl instead gets the whole document.
|
|
|
|
FTP and SFTP range downloads only support the simple 'start-stop' syntax
|
|
(optionally with one of the numbers omitted). FTP use depends on the extended
|
|
FTP command SIZE.
|