Artifactspublic-v0

curl

master
ply4 git calls117 ms288 KiB2 cachedprotocol v2
100 lines2.5 KiBRaw

NAME

CURLOPT_RANGE - byte range to request

SYNOPSIS

c
#include <curl/curl.h>

CURLcode curl_easy_setopt(CURL *handle, CURLOPT_RANGE, char *range);

DESCRIPTION

Pass a char pointer as parameter, which should contain the specified range you want to retrieve. It should be in the format "X-Y", where either X or Y may be left out and X and Y are byte indexes.

HTTP transfers also support several intervals, separated with commas as in "X-Y,N-M". Using this kind of multiple intervals causes the HTTP server to send the response document in pieces (using standard MIME separation techniques) as a multiple part response which libcurl 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.

Unfortunately, the HTTP standard (RFC 7233 section 3.1) allows servers to ignore range requests so even when you set CURLOPT_RANGE(3) for a request, you may end up getting the full response sent back.

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.

For HTTP PUT uploads this option should not be used, since it may conflict with other options.

Using this option multiple times makes the last set string override the previous ones. Set it to NULL to disable its use again.

The application does not have to keep the string around after setting this option.

DEFAULT

NULL

%PROTOCOLS%

EXAMPLE

c
int main(void)
{
  CURL *curl = curl_easy_init();
  if(curl) {
    CURLcode result;
    curl_easy_setopt(curl, CURLOPT_URL, "https://example.com");

    /* get the first 200 bytes */
    curl_easy_setopt(curl, CURLOPT_RANGE, "0-199");

    /* Perform the request */
    result = curl_easy_perform(curl);
    curl_easy_cleanup(curl);
  }
}

HISTORY

FILE since 7.18.0, RTSP since 7.20.0

%AVAILABILITY%

RETURN VALUE

curl_easy_setopt(3) returns a CURLcode indicating success or error.

CURLE_OK (0) means everything was OK, non-zero means an error occurred, see libcurl-errors(3).

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Title: CURLOPT_RANGE
5Section: 3
6Source: libcurl
7See-also:
8 - CURLOPT_LOW_SPEED_LIMIT (3)
9 - CURLOPT_MAXFILESIZE_LARGE (3)
10 - CURLOPT_MAX_RECV_SPEED_LARGE (3)
11 - CURLOPT_RESUME_FROM (3)
12Protocol:
13 - HTTP
14 - FTP
15 - FILE
16 - RTSP
17 - SFTP
18Added-in: 7.1
19---
21# NAME
23CURLOPT_RANGE - byte range to request
25# SYNOPSIS
27~~~c
28#include <curl/curl.h>
30CURLcode curl_easy_setopt(CURL *handle, CURLOPT_RANGE, char *range);
31~~~
33# DESCRIPTION
35Pass a char pointer as parameter, which should contain the specified range you
36want to retrieve. It should be in the format "X-Y", where either X or Y may be
37left out and X and Y are byte indexes.
39HTTP transfers also support several intervals, separated with commas as in
40*"X-Y,N-M"*. Using this kind of multiple intervals causes the HTTP server
41to send the response document in pieces (using standard MIME separation
42techniques) as a multiple part response which libcurl returns as-is. It
43contains meta information in addition to the requested bytes. Parsing or
44otherwise transforming this response is the responsibility of the caller.
46Unfortunately, the HTTP standard (RFC 7233 section 3.1) allows servers to
47ignore range requests so even when you set CURLOPT_RANGE(3) for a request, you
48may end up getting the full response sent back.
50For RTSP, the formatting of a range should follow RFC 2326 Section 12.29. For
51RTSP, byte ranges are **not** permitted. Instead, ranges should be given in
52**npt**, **utc**, or **smpte** formats.
54For HTTP PUT uploads this option should not be used, since it may conflict with
55other options.
57Using this option multiple times makes the last set string override the
58previous ones. Set it to NULL to disable its use again.
60The application does not have to keep the string around after setting this
61option.
63# DEFAULT
65NULL
67# %PROTOCOLS%
69# EXAMPLE
71~~~c
72int main(void)
74 CURL *curl = curl_easy_init();
75 if(curl) {
76 CURLcode result;
77 curl_easy_setopt(curl, CURLOPT_URL, "https://example.com");
79 /* get the first 200 bytes */
80 curl_easy_setopt(curl, CURLOPT_RANGE, "0-199");
82 /* Perform the request */
83 result = curl_easy_perform(curl);
84 curl_easy_cleanup(curl);
85 }
87~~~
89# HISTORY
91FILE since 7.18.0, RTSP since 7.20.0
93# %AVAILABILITY%
95# RETURN VALUE
97curl_easy_setopt(3) returns a CURLcode indicating success or error.
99CURLE_OK (0) means everything was OK, non-zero means an error occurred, see
100libcurl-errors(3).
Diagnostics4 git calls · 117 ms
CallStatusSizeTime0117 ms
discover200152 B2 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
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 · hit2 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=2
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=2
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.4 KiB112 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=112
git.response.bytes=1422
git.response.cache=MISS
git.response.duration_ms=112
git.fetch.wants=4f7f1a88b273f2302846866fb5480b22a5cd3e8f
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=1422
git.pkt.payload.max=1401
git.sideband.band1.bytes=1400
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
a5e34971295d4652
Request
2604824f…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format