Artifactspublic-v0

curl

master
ply4 git calls139 ms288 KiB2 cachedprotocol v2
66 lines2.0 KiBRaw

--range

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.

0-499

specifies the first 500 bytes

500-999

specifies the second 500 bytes

-500

specifies the last 500 bytes

9500-

specifies the bytes from offset 9500 and forward

0-0,-1

specifies the first and last byte only(*)(HTTP)

100-199,500-599

specifies two separate 100-byte ranges(*) (HTTP)

(*) = NOTE that if specifying multiple ranges and the server supports it then it replies with a multiple part response that curl returns as-is. It contains meta information in addition to the requested bytes. 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.

When using this option for HTTP uploads using POST or PUT, functionality is not guaranteed. The HTTP protocol has no standard interoperable resume upload and curl uses a set of headers for this purpose that once proved working for some servers and have been left for those who find that useful.

This command line option is mutually exclusive with --continue-at: you can only use one of them for a single transfer.

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Long: range
5Short: r
6Help: Retrieve only the bytes within RANGE
7Arg: <range>
8Protocols: HTTP FTP SFTP FILE
9Category: http ftp sftp file
10Added: 4.0
11Multi: single
12See-also:
13 - continue-at
14 - append
15Example:
16 - --range 22-44 $URL
17---
19# `--range`
21Retrieve a byte range (i.e. a partial document) from an HTTP/1.1, FTP or SFTP
22server or a local FILE. Ranges can be specified in a number of ways.
24## 0-499
25specifies the first 500 bytes
27## 500-999
28specifies the second 500 bytes
30## -500
31specifies the last 500 bytes
33## 9500-
34specifies the bytes from offset 9500 and forward
36## 0-0,-1
37specifies the first and last byte only(*)(HTTP)
39## 100-199,500-599
40specifies two separate 100-byte ranges(*) (HTTP)
42##
44(*) = NOTE that if specifying multiple ranges and the server supports it then
45it replies with a multiple part response that curl returns as-is. It
46contains meta information in addition to the requested bytes. Parsing or
47otherwise transforming this response is the responsibility of the caller.
49Only digit characters (0-9) are valid in the 'start' and 'stop' fields of the
50'start-stop' range syntax. If a non-digit character is given in the range, the
51server's response is unspecified, depending on the server's configuration.
53Many HTTP/1.1 servers do not have this feature enabled, so that when you
54attempt to get a range, curl instead gets the whole document.
56FTP and SFTP range downloads only support the simple 'start-stop' syntax
57(optionally with one of the numbers omitted). FTP use depends on the extended
58FTP command SIZE.
60When using this option for HTTP uploads using POST or PUT, functionality is
61not guaranteed. The HTTP protocol has no standard interoperable resume upload
62and curl uses a set of headers for this purpose that once proved working for
63some servers and have been left for those who find that useful.
65This command line option is mutually exclusive with --continue-at: you can only
66use one of them for a single transfer.
Diagnostics4 git calls · 139 ms
CallStatusSizeTime0139 ms
discover200152 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=3
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit3 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=3
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit3 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=133
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=3
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2001.1 KiB133 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=1141
git.response.cache=MISS
git.response.duration_ms=133
git.fetch.wants=ab1b126575672a07d953597b375fe00111fc8610
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=1141
git.pkt.payload.max=1120
git.sideband.band1.bytes=1119
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e32361c9cd5aae
Request
54be36f1…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format