Artifactspublic-v0

curl

master
ply4 git calls32 ms289 KiB3 cachedprotocol v2
137 lines4.3 KiBRaw

Experimental

Some features and functionality in curl and libcurl are considered EXPERIMENTAL.

Experimental support in curl means:

  1. Experimental features are provided to allow users to try them out and provide feedback on functionality and API etc before they ship and get "carved in stone".
  2. You must enable the feature when invoking configure as otherwise curl is not built with the feature present.
  3. We strongly advise against using this feature in production.
  4. We reserve the right to change behavior of the feature without sticking to our API/ABI rules as we do for regular features, as long as it is marked experimental.
  5. Experimental features are clearly marked so in documentation. Beware.
  6. Vulnerabilities in experimental features are not considered security problems; please report them as regular bugs/feedback instead.

Graduation

  1. Each experimental feature should have a set of documented requirements of what is needed for that feature to graduate. Graduation means being removed from the list of experiments.
  2. An experiment should NOT graduate if it needs test cases to be disabled, unless they are for minor features that are clearly documented as not provided by the experiment and then the disabling should be managed inside each affected test case.

The quiche QUIC and HTTP/3 backend

Graduation requirements:

  • The library should be considered out-of-beta

  • a reasonable expectation of a stable API going forward

  • HTTP/3 with the given build should perform without risking busy-loops

HTTP/3 proxy and CONNECT-UDP support

Support for HTTP/3 proxy and CONNECT-UDP tunneling is experimental and requires an explicit build-time opt-in (--enable-proxy-http3 for autotools, -DUSE_PROXY_HTTP3=ON for CMake).

Graduation requirements:

  • implementation stability over time with no known severe regressions

The Rustls TLS backend

Graduation requirements:

  • a reasonable expectation of a stable API going forward.

ECH

Use of the HTTPS resource record and Encrypted Client Hello (ECH) when using DoH

Graduation requirements:

  • ECH support exists in at least one widely used TLS library apart from BoringSSL and wolfSSL.

  • feedback from users saying that ECH works for their use cases

  • it has been given time to mature, so no earlier than April 2025 (twelve months after being added here)

SSL session import/export

Import/Export of SSL sessions tickets in libcurl and curl command line option '--ssl-session <filename>' for faster TLS handshakes and use of TLSv1.3/QUIC Early Data (0-RTT).

Graduation requirements:

  • the implementation is considered safe

  • feedback from users saying that session export works for their use cases

HTTPS RR

HTTPS records support is a requirement for ECH but is provided as a stand-alone feature that is itself considered EXPERIMENTAL.

Graduation requirements:

  • HTTPS records work for DoH, c-ares and the threaded resolver

  • HTTPS records can control ALPN and port number, at least

  • There are options to control HTTPS use

HTTP Message Signatures (RFC 9421)

Sign outgoing HTTP requests according to RFC 9421 using the --httpsig-algo, --httpsig-key, --httpsig-keyid and --httpsig-headers command line options, or the corresponding CURLOPT_HTTPSIG_* libcurl options. Built only when configured with --enable-httpsig.

Graduation requirements:

  • the option set (names, arguments, defaults) is settled

  • interoperability has been verified against at least two independent RFC 9421 implementations

  • no test cases are disabled for the feature

  • feedback from users saying the API works for their use cases

Apple fast UDP

There are undocumented system calls available in Apple operating systems that when used allow for faster sending and receiving of UDP messages.

The undocumented and thus unsupported-by-Apple nature of these functions brings a risk that they are removed in a future OS update, or perhaps worse: marginally modified to instead cause subtle and hard-to-spot bugs.

Graduation requirements:

  • testimonials from users that these work reliably

  • measurements that show they make a measurable performance impact

  • an easy way to (re-)build curl to not use these functions

1<!--
2Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
4SPDX-License-Identifier: curl
5-->
7# Experimental
9Some features and functionality in curl and libcurl are considered
10**EXPERIMENTAL**.
12Experimental support in curl means:
141. Experimental features are provided to allow users to try them out and
15 provide feedback on functionality and API etc before they ship and get
16 "carved in stone".
172. You must enable the feature when invoking configure as otherwise curl is
18 not built with the feature present.
193. We strongly advise against using this feature in production.
204. **We reserve the right to change behavior** of the feature without sticking
21 to our API/ABI rules as we do for regular features, as long as it is marked
22 experimental.
235. Experimental features are clearly marked so in documentation. Beware.
246. Vulnerabilities in experimental features are not considered security
25 problems; please report them as regular bugs/feedback instead.
27## Graduation
291. Each experimental feature should have a set of documented requirements of
30 what is needed for that feature to graduate. Graduation means being removed
31 from the list of experiments.
322. An experiment should NOT graduate if it needs test cases to be disabled,
33 unless they are for minor features that are clearly documented as not
34 provided by the experiment and then the disabling should be managed inside
35 each affected test case.
37## The quiche QUIC and HTTP/3 backend
39Graduation requirements:
41- The library should be considered out-of-beta
43- a reasonable expectation of a stable API going forward
45- HTTP/3 with the given build should perform without risking busy-loops
47## HTTP/3 proxy and CONNECT-UDP support
49Support for HTTP/3 proxy and CONNECT-UDP tunneling is experimental and
50requires an explicit build-time opt-in (`--enable-proxy-http3` for
51autotools, `-DUSE_PROXY_HTTP3=ON` for CMake).
53Graduation requirements:
55- implementation stability over time with no known severe regressions
57## The Rustls TLS backend
59Graduation requirements:
61- a reasonable expectation of a stable API going forward.
63## ECH
65Use of the HTTPS resource record and Encrypted Client Hello (ECH) when using
66DoH
68Graduation requirements:
70- ECH support exists in at least one widely used TLS library apart from
71 BoringSSL and wolfSSL.
73- feedback from users saying that ECH works for their use cases
75- it has been given time to mature, so no earlier than April 2025 (twelve
76 months after being added here)
78## SSL session import/export
80Import/Export of SSL sessions tickets in libcurl and curl command line
81option '--ssl-session <filename>' for faster TLS handshakes and use
82of TLSv1.3/QUIC Early Data (0-RTT).
84Graduation requirements:
86- the implementation is considered safe
88- feedback from users saying that session export works for their use cases
90## HTTPS RR
92HTTPS records support is a requirement for ECH but is provided as a
93stand-alone feature that is itself considered EXPERIMENTAL.
95Graduation requirements:
97- HTTPS records work for DoH, c-ares and the threaded resolver
99- HTTPS records can control ALPN and port number, at least
101- There are options to control HTTPS use
103## HTTP Message Signatures (RFC 9421)
105Sign outgoing HTTP requests according to RFC 9421 using the
106`--httpsig-algo`, `--httpsig-key`, `--httpsig-keyid` and
107`--httpsig-headers` command line options, or the corresponding
108`CURLOPT_HTTPSIG_*` libcurl options. Built only when configured with
109`--enable-httpsig`.
111Graduation requirements:
113- the option set (names, arguments, defaults) is settled
115- interoperability has been verified against at least two independent
116 RFC 9421 implementations
118- no test cases are disabled for the feature
120- feedback from users saying the API works for their use cases
122## Apple fast UDP
124There are undocumented system calls available in Apple operating systems that
125when used allow for faster sending and receiving of UDP messages.
127The undocumented and thus unsupported-by-Apple nature of these functions
128brings a risk that they are removed in a future OS update, or perhaps worse:
129marginally modified to instead cause subtle and hard-to-spot bugs.
131Graduation requirements:
133- testimonials from users that these work reliably
135- measurements that show they make a measurable performance impact
137- an easy way to (re-)build curl to not use these functions
Diagnostics4 git calls · 32 ms
CallStatusSizeTime032 ms
discover200152 B2 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 · 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=27
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
fetch2002.0 KiB · hit27 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=2048
git.response.cache=HIT
git.response.duration_ms=27
git.fetch.wants=51407743ee39c9908b6da44eae92410b56d344b5
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=2048
git.pkt.payload.max=2027
git.sideband.band1.bytes=2026
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
a5e14ab3bb09a140
Request
e03c8271…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format