Artifactspublic-v0

curl

master
ply4 git calls93 ms291 KiB3 cachedprotocol v2
278 lines11 KiBRaw

curl cipher options

A TLS handshake involves many parameters which take part in the negotiation between client and server in order to agree on the TLS version and set of algorithms to use for a connection.

What has become known as a "cipher" or better "cipher suite" in TLS are names for specific combinations of key exchange, bulk encryption, message authentication code and with TLSv1.3 the authenticated encryption. In addition, there are other parameters that influence the TLS handshake, like DHE "groups" and ECDHE with its "curves".

History

curl's way of letting users configure these settings closely followed OpenSSL in its API. TLS learned new parameters, OpenSSL added new API functions and curl added command line options.

Several other TLS backends followed the OpenSSL approach, more or less closely, and curl maps the command line options to these TLS backends. Some TLS backends do not support all of it and command line options are either ignored or lead to an error.

Many examples below show the OpenSSL-like use of these options. GnuTLS however chose a different approach. These are described in a separate section further below.

ciphers, the OpenSSL way

With curl's option --tls13-ciphers or CURLOPT_TLS13_CIPHERS users can control which cipher suites to consider when negotiating TLS 1.3 connections. With option --ciphers or CURLOPT_SSL_CIPHER_LIST users can control which cipher suites to consider when negotiating TLS 1.2 (1.1, 1.0) connections.

By default, curl may negotiate TLS 1.3 and TLS 1.2 connections, so the cipher suites considered when negotiating a TLS connection are a union of the TLS 1.3 and TLS 1.2 cipher suites. If you want curl to consider only TLS 1.3 cipher suites for the connection, you have to set the minimum TLS version to 1.3 by using --tlsv1.3 or CURLOPT_SSLVERSION with CURL_SSLVERSION_TLSv1_3.

Both the TLS 1.3 and TLS 1.2 cipher options expect a list of cipher suites separated by colons (:). This list is parsed opportunistically, cipher suites that are not recognized or implemented are ignored. As long as there is at least one recognized cipher suite in the list, the list is considered valid.

For both the TLS 1.3 and TLS 1.2 cipher options, the order in which the cipher suites are specified determine the preference of them. When negotiating a TLS connection the server picks a cipher suite from the intersection of the cipher suites supported by the server and the cipher suites sent by curl. If the server is configured to honor the client's cipher preference, the first common cipher suite in the list sent by curl is chosen.

TLS 1.3 cipher suites

Setting TLS 1.3 cipher suites is supported by curl with OpenSSL (1.1.1+, curl 7.61.0+), LibreSSL (3.4.1+, curl 8.3.0+), wolfSSL (curl 8.10.0+) and mbedTLS (3.6.0+, curl 8.10.0+).

The list of cipher suites that can be used for the --tls13-ciphers option:

TLS_AES_128_GCM_SHA256
TLS_AES_256_GCM_SHA384
TLS_CHACHA20_POLY1305_SHA256
TLS_AES_128_CCM_SHA256
TLS_AES_128_CCM_8_SHA256
wolfSSL notes

In addition to above list the following cipher suites can be used: TLS_SM4_GCM_SM3 TLS_SM4_CCM_SM3 TLS_SHA256_SHA256 TLS_SHA384_SHA384. Usage of these cipher suites is not recommended. (The last two cipher suites are NULL ciphers, offering no encryption whatsoever.)

TLS 1.2 (1.1, 1.0) cipher suites

Setting TLS 1.2 cipher suites is supported by curl with AWS-LC, BoringSSL, LibreSSL, mbedTLS (curl 8.8.0+), OpenSSL, wolfSSL (curl 7.53.0+). Schannel does not support setting cipher suites directly, but does support setting algorithms (curl 7.61.0+), see Schannel notes below.

For TLS 1.2 cipher suites there are multiple naming schemes, the two most used are with OpenSSL names (e.g. ECDHE-RSA-AES128-GCM-SHA256) and IANA names (e.g. TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256). IANA names of TLS 1.2 cipher suites look similar to TLS 1.3 cipher suite names, to distinguish them note that TLS 1.2 names contain _WITH_, while TLS 1.3 names do not. When setting TLS 1.2 cipher suites with curl it is recommended that you use OpenSSL names as these are most widely recognized by the supported SSL backends.

The complete list of cipher suites that may be considered for the --ciphers option is extensive, it consists of more than 300 ciphers suites. Nowadays, most of them are discouraged, and support for a lot of them has been removed from the various SSL backends, if ever implemented at all.

A shortened list (based on recommendations by Mozilla) of cipher suites, which are (mostly) supported by all SSL backends, that can be used for the --ciphers option:

ECDHE-ECDSA-AES128-GCM-SHA256
ECDHE-RSA-AES128-GCM-SHA256
ECDHE-ECDSA-AES256-GCM-SHA384
ECDHE-RSA-AES256-GCM-SHA384
ECDHE-ECDSA-CHACHA20-POLY1305
ECDHE-RSA-CHACHA20-POLY1305
DHE-RSA-AES128-GCM-SHA256
DHE-RSA-AES256-GCM-SHA384
DHE-RSA-CHACHA20-POLY1305
ECDHE-ECDSA-AES128-SHA256
ECDHE-RSA-AES128-SHA256
ECDHE-ECDSA-AES128-SHA
ECDHE-RSA-AES128-SHA
ECDHE-ECDSA-AES256-SHA384
ECDHE-RSA-AES256-SHA384
ECDHE-ECDSA-AES256-SHA
ECDHE-RSA-AES256-SHA
DHE-RSA-AES128-SHA256
DHE-RSA-AES256-SHA256
AES128-GCM-SHA256
AES256-GCM-SHA384
AES128-SHA256
AES256-SHA256
AES128-SHA
AES256-SHA
DES-CBC3-SHA

See this list for a complete list of TLS 1.2 cipher suites.

OpenSSL notes

In addition to specifying a list of cipher suites, OpenSSL also accepts a format with specific cipher strings (like TLSv1.2, AESGCM, CHACHA20) and !, - and + operators. Refer to the OpenSSL cipher documentation for further information on that format.

Schannel notes

Schannel does not support setting individual TLS 1.2 cipher suites directly. It only allows the enabling and disabling of encryption algorithms. These are in the form of CALG_xxx, see the Schannel ALG_ID documentation for a list of these algorithms. Also, (since curl 7.77.0) SCH_USE_STRONG_CRYPTO can be given to pass that flag to Schannel, lookup the documentation for the Windows version in use to see how that affects the cipher suite selection. When not specifying the --ciphers and --tls13-ciphers options curl passes this flag by default.

Examples

sh
curl \
  --tls13-ciphers TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256 \
  --ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:\
ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305 \
  https://example.com/

Restrict ciphers to aes128-gcm and chacha20. Works with OpenSSL, LibreSSL, mbedTLS and wolfSSL.

sh
curl \
  --tlsv1.3 \
  --tls-max 1.3 \
  --tls13-ciphers TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256 \
  https://example.com/

Restrict to only TLS 1.3 with aes128-gcm and chacha20 ciphers. Works with OpenSSL, LibreSSL, mbedTLS and wolfSSL.

sh
curl \
  --ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:\
ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305 \
  https://example.com/

Restrict TLS 1.2 ciphers to aes128-gcm and chacha20, use default TLS 1.3 ciphers (if TLS 1.3 is available). Works with OpenSSL, LibreSSL, BoringSSL, mbedTLS and wolfSSL.

ciphers, the GnuTLS way

With GnuTLS, curl allows configuration of all TLS parameters via option --ciphers or CURLOPT_SSL_CIPHER_LIST only. The option --tls13-ciphers or CURLOPT_TLS13_CIPHERS is being ignored.

--ciphers is used to set the GnuTLS priority string in the following way:

  • When the set string starts with '+', '-' or '!' it is appended to the priority string libcurl itself generates (separated by ':'). This initial priority depends other settings such as CURLOPT_SSLVERSION(3) or if HTTP/3 (QUIC) is being negotiated.
  • Otherwise, the set string fully replaces the libcurl generated one. While giving full control to the application, the set priority needs to provide for everything the transfer may need to negotiate. Example: if the set priority only allows TLSv1.2, all HTTP/3 attempts fail.

Users may specify via --ciphers anything that GnuTLS supports: ciphers, key exchange, MAC, compression, TLS versions, signature algorithms, groups, elliptic curves, certificate types. In addition, GnuTLS has a variety of other keywords that tweak its operations. Applications or a system may define new alias names for priority strings that can then be used here.

Since the order of items in priority strings is significant, it makes no sense for curl to puzzle other SSL options somehow together. --ciphers is the single way to change priority.

Examples

sh
curl \
  --ciphers '-CIPHER_ALL:+AES-128-GCM:+CHACHA20-POLY1305' \
  https://example.com/

Restrict ciphers to aes128-gcm and chacha20 in GnuTLS.

sh
curl \
  --ciphers 'NORMAL:-VERS-ALL:+TLS1.3:-AES-256-GCM' \
  https://example.com/

Restrict to only TLS 1.3 without the aes256-gcm cipher.

sh
curl \
  --ciphers 'NORMAL:-VERS-ALL:+TLS1.2:-CIPHER_ALL:+CAMELLIA-128-GCM' \
  https://example.com/

Restrict to only TLS 1.2 with the CAMELLIA-128-GCM cipher.

Further reading

1<!--
2Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
4SPDX-License-Identifier: curl
5-->
7## curl cipher options
9A TLS handshake involves many parameters which take part in the negotiation
10between client and server in order to agree on the TLS version and set of
11algorithms to use for a connection.
13What has become known as a "cipher" or better "cipher suite" in TLS
14are names for specific combinations of
15[key exchange](https://en.wikipedia.org/wiki/Key_exchange),
16[bulk encryption](https://en.wikipedia.org/wiki/Link_encryption),
17[message authentication code](https://en.wikipedia.org/wiki/Message_authentication_code)
18and with TLSv1.3 the
19[authenticated encryption](https://en.wikipedia.org/wiki/Authenticated_encryption).
20In addition, there are other parameters that influence the TLS handshake, like
21[DHE](https://en.wikipedia.org/wiki/Diffie%e2%80%93Hellman_key_exchange) "groups"
22and [ECDHE](https://en.wikipedia.org/wiki/Elliptic-curve_Diffie%e2%80%93Hellman)
23with its "curves".
25### History
27curl's way of letting users configure these settings closely followed OpenSSL
28in its API. TLS learned new parameters, OpenSSL added new API functions and
29curl added command line options.
31Several other TLS backends followed the OpenSSL approach, more or less closely,
32and curl maps the command line options to these TLS backends. Some TLS
33backends do not support all of it and command line options are either
34ignored or lead to an error.
36Many examples below show the OpenSSL-like use of these options. GnuTLS
37however chose a different approach. These are described in a separate
38section further below.
40## ciphers, the OpenSSL way
42With curl's option
43[`--tls13-ciphers`](https://curl.se/docs/manpage.html#--tls13-ciphers)
44or
45[`CURLOPT_TLS13_CIPHERS`](https://curl.se/libcurl/c/CURLOPT_TLS13_CIPHERS.html)
46users can control which cipher suites to consider when negotiating TLS 1.3
47connections. With option
48[`--ciphers`](https://curl.se/docs/manpage.html#--ciphers)
49or
50[`CURLOPT_SSL_CIPHER_LIST`](https://curl.se/libcurl/c/CURLOPT_SSL_CIPHER_LIST.html)
51users can control which cipher suites to consider when negotiating
52TLS 1.2 (1.1, 1.0) connections.
54By default, curl may negotiate TLS 1.3 and TLS 1.2 connections, so the cipher
55suites considered when negotiating a TLS connection are a union of the TLS 1.3
56and TLS 1.2 cipher suites. If you want curl to consider only TLS 1.3 cipher
57suites for the connection, you have to set the minimum TLS version to 1.3 by
58using [`--tlsv1.3`](https://curl.se/docs/manpage.html#--tlsv13)
59or [`CURLOPT_SSLVERSION`](https://curl.se/libcurl/c/CURLOPT_SSLVERSION.html)
60with `CURL_SSLVERSION_TLSv1_3`.
62Both the TLS 1.3 and TLS 1.2 cipher options expect a list of cipher suites
63separated by colons (`:`). This list is parsed opportunistically, cipher suites
64that are not recognized or implemented are ignored. As long as there is at
65least one recognized cipher suite in the list, the list is considered valid.
67For both the TLS 1.3 and TLS 1.2 cipher options, the order in which the
68cipher suites are specified determine the preference of them. When negotiating
69a TLS connection the server picks a cipher suite from the intersection of the
70cipher suites supported by the server and the cipher suites sent by curl. If
71the server is configured to honor the client's cipher preference, the first
72common cipher suite in the list sent by curl is chosen.
74### TLS 1.3 cipher suites
76Setting TLS 1.3 cipher suites is supported by curl with
77OpenSSL (1.1.1+, curl 7.61.0+), LibreSSL (3.4.1+, curl 8.3.0+),
78wolfSSL (curl 8.10.0+) and mbedTLS (3.6.0+, curl 8.10.0+).
80The list of cipher suites that can be used for the `--tls13-ciphers` option:
82```
83TLS_AES_128_GCM_SHA256
84TLS_AES_256_GCM_SHA384
85TLS_CHACHA20_POLY1305_SHA256
86TLS_AES_128_CCM_SHA256
87TLS_AES_128_CCM_8_SHA256
88```
90#### wolfSSL notes
92In addition to above list the following cipher suites can be used:
93`TLS_SM4_GCM_SM3` `TLS_SM4_CCM_SM3` `TLS_SHA256_SHA256` `TLS_SHA384_SHA384`.
94Usage of these cipher suites is not recommended. (The last two cipher suites
95are NULL ciphers, offering no encryption whatsoever.)
97### TLS 1.2 (1.1, 1.0) cipher suites
99Setting TLS 1.2 cipher suites is supported by curl with AWS-LC, BoringSSL,
100LibreSSL, mbedTLS (curl 8.8.0+), OpenSSL, wolfSSL (curl 7.53.0+). Schannel
101does not support setting cipher suites directly, but does support setting
102algorithms (curl 7.61.0+), see Schannel notes below.
104For TLS 1.2 cipher suites there are multiple naming schemes, the two most used
105are with OpenSSL names (e.g. `ECDHE-RSA-AES128-GCM-SHA256`) and IANA names
106(e.g. `TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`). IANA names of TLS 1.2 cipher
107suites look similar to TLS 1.3 cipher suite names, to distinguish them note
108that TLS 1.2 names contain `_WITH_`, while TLS 1.3 names do not. When setting
109TLS 1.2 cipher suites with curl it is recommended that you use OpenSSL names
110as these are most widely recognized by the supported SSL backends.
112The complete list of cipher suites that may be considered for the `--ciphers`
113option is extensive, it consists of more than 300 ciphers suites. Nowadays,
114most of them are discouraged, and support for a lot of them has been removed
115from the various SSL backends, if ever implemented at all.
117A shortened list (based on [recommendations by
118Mozilla](https://wiki.mozilla.org/Security/Server_Side_TLS)) of cipher suites,
119which are (mostly) supported by all SSL backends, that can be used for the
120`--ciphers` option:
122```
123ECDHE-ECDSA-AES128-GCM-SHA256
124ECDHE-RSA-AES128-GCM-SHA256
125ECDHE-ECDSA-AES256-GCM-SHA384
126ECDHE-RSA-AES256-GCM-SHA384
127ECDHE-ECDSA-CHACHA20-POLY1305
128ECDHE-RSA-CHACHA20-POLY1305
129DHE-RSA-AES128-GCM-SHA256
130DHE-RSA-AES256-GCM-SHA384
131DHE-RSA-CHACHA20-POLY1305
132ECDHE-ECDSA-AES128-SHA256
133ECDHE-RSA-AES128-SHA256
134ECDHE-ECDSA-AES128-SHA
135ECDHE-RSA-AES128-SHA
136ECDHE-ECDSA-AES256-SHA384
137ECDHE-RSA-AES256-SHA384
138ECDHE-ECDSA-AES256-SHA
139ECDHE-RSA-AES256-SHA
140DHE-RSA-AES128-SHA256
141DHE-RSA-AES256-SHA256
142AES128-GCM-SHA256
143AES256-GCM-SHA384
144AES128-SHA256
145AES256-SHA256
146AES128-SHA
147AES256-SHA
148DES-CBC3-SHA
149```
151See this [list](https://github.com/curl/curl/blob/master/docs/CIPHERS-TLS12.md)
152for a complete list of TLS 1.2 cipher suites.
154#### OpenSSL notes
156In addition to specifying a list of cipher suites, OpenSSL also accepts a
157format with specific cipher strings (like `TLSv1.2`, `AESGCM`, `CHACHA20`) and
158`!`, `-` and `+` operators. Refer to the
159[OpenSSL cipher documentation](https://docs.openssl.org/master/man1/openssl-ciphers/#cipher-list-format)
160for further information on that format.
162#### Schannel notes
164Schannel does not support setting individual TLS 1.2 cipher suites directly.
165It only allows the enabling and disabling of encryption algorithms. These are
166in the form of `CALG_xxx`, see the [Schannel `ALG_ID`
167documentation](https://learn.microsoft.com/windows/win32/seccrypto/alg-id)
168for a list of these algorithms. Also, (since curl 7.77.0)
169`SCH_USE_STRONG_CRYPTO` can be given to pass that flag to Schannel, lookup the
170[documentation for the Windows version in
171use](https://learn.microsoft.com/windows/win32/secauthn/cipher-suites-in-schannel)
172to see how that affects the cipher suite selection. When not specifying the
173`--ciphers` and `--tls13-ciphers` options curl passes this flag by default.
175### Examples
177```sh
178curl \
179 --tls13-ciphers TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256 \
180 --ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:\
181ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305 \
182 https://example.com/
183```
185Restrict ciphers to `aes128-gcm` and `chacha20`. Works with OpenSSL, LibreSSL,
186mbedTLS and wolfSSL.
188```sh
189curl \
190 --tlsv1.3 \
191 --tls-max 1.3 \
192 --tls13-ciphers TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256 \
193 https://example.com/
194```
196Restrict to only TLS 1.3 with `aes128-gcm` and `chacha20` ciphers. Works with
197OpenSSL, LibreSSL, mbedTLS and wolfSSL.
199```sh
200curl \
201 --ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:\
202ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305 \
203 https://example.com/
204```
206Restrict TLS 1.2 ciphers to `aes128-gcm` and `chacha20`, use default TLS 1.3
207ciphers (if TLS 1.3 is available). Works with OpenSSL, LibreSSL, BoringSSL,
208mbedTLS and wolfSSL.
210## ciphers, the GnuTLS way
212With GnuTLS, curl allows configuration of all TLS parameters via option
213[`--ciphers`](https://curl.se/docs/manpage.html#--ciphers)
214or
215[`CURLOPT_SSL_CIPHER_LIST`](https://curl.se/libcurl/c/CURLOPT_SSL_CIPHER_LIST.html)
216only. The option
217[`--tls13-ciphers`](https://curl.se/docs/manpage.html#--tls13-ciphers)
218or
219[`CURLOPT_TLS13_CIPHERS`](https://curl.se/libcurl/c/CURLOPT_TLS13_CIPHERS.html)
220is being ignored.
222`--ciphers` is used to set the GnuTLS **priority string** in
223the following way:
225* When the set string starts with '+', '-' or '!' it is *appended* to the
226 priority string libcurl itself generates (separated by ':'). This initial
227 priority depends other settings such as CURLOPT_SSLVERSION(3) or if HTTP/3
228 (QUIC) is being negotiated.
229* Otherwise, the set string fully *replaces* the libcurl generated one. While
230 giving full control to the application, the set priority needs to
231 provide for everything the transfer may need to negotiate. Example: if
232 the set priority only allows TLSv1.2, all HTTP/3 attempts fail.
234Users may specify via `--ciphers` anything that GnuTLS supports: ciphers,
235key exchange, MAC, compression, TLS versions, signature algorithms, groups,
236elliptic curves, certificate types. In addition, GnuTLS has a variety of
237other keywords that tweak its operations. Applications or a system
238may define new alias names for priority strings that can then be used here.
240Since the order of items in priority strings is significant, it makes no
241sense for curl to puzzle other SSL options somehow together. `--ciphers`
242is the single way to change priority.
244### Examples
246```sh
247curl \
248 --ciphers '-CIPHER_ALL:+AES-128-GCM:+CHACHA20-POLY1305' \
249 https://example.com/
250```
252Restrict ciphers to `aes128-gcm` and `chacha20` in GnuTLS.
254```sh
255curl \
256 --ciphers 'NORMAL:-VERS-ALL:+TLS1.3:-AES-256-GCM' \
257 https://example.com/
258```
260Restrict to only TLS 1.3 without the `aes256-gcm` cipher.
262```sh
263curl \
264 --ciphers 'NORMAL:-VERS-ALL:+TLS1.2:-CIPHER_ALL:+CAMELLIA-128-GCM' \
265 https://example.com/
266```
268Restrict to only TLS 1.2 with the `CAMELLIA-128-GCM` cipher.
270## Further reading
272- [GnuTLS Priority Strings](https://gnutls.org/manual/html_node/Priority-Strings.html)
273- [IANA cipher suites list](https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-4)
274- [mbedTLS cipher suites reference](https://mbed-tls.readthedocs.io/projects/api/en/development/api/file/ssl__ciphersuites_8h/)
275- [OpenSSL cipher suite names documentation](https://docs.openssl.org/master/man1/openssl-ciphers/#cipher-suite-names)
276- [Schannel cipher suites documentation](https://learn.microsoft.com/windows/win32/secauthn/cipher-suites-in-schannel)
277- [Wikipedia cipher suite article](https://en.wikipedia.org/wiki/Cipher_suite)
278- [wolfSSL cipher support documentation](https://www.wolfssl.com/documentation/manuals/wolfssl/chapter04.html#cipher-support)
Diagnostics4 git calls · 93 ms
CallStatusSizeTime093 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 · hit5 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 · hit41 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=3
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=41
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
fetch2004.0 KiB · hit47 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=46
git.response.bytes=4141
git.response.cache=HIT
git.response.duration_ms=47
git.fetch.wants=0c1c3db666ce2477b922bb7a4aa6c203899fcd9f
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=4141
git.pkt.payload.max=4120
git.sideband.band1.bytes=4119
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
a5e1c313afcf36cd
Request
5ebea4fa…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format