test(interop): the clients against real sites over the internet, and quic-interop-runner

Aperta
#57 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c

Direzione di ricerca

The existing local harness is tests/servers/run.sh, and the clients involved are h2_client and h3_client. Start by reading those two entry points and the script to see how a run is launched and how results are reported. The work has two parts: running the clients against public origins with recorded results, and wrapping the client and server in the quic-interop-runner Docker images. Done means both runs are written up in H2H3.md with every failure fixed or listed as a known limit.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

P0: release blocker

Every interop test so far is local: a simulated network, ngtcp2, nghttp2 and nghttp3 in memory, and real servers on 127.0.0.1 (tests/servers/run.sh). CDNs behave differently from the reference stacks (Retry under load, small MTUs, connection-ID rotation, 0-RTT policies, GOAWAY timing), and real paths add loss and reordering the simulator doesn't model.

  1. The clients against real sites over the internet: h2_client (TLS + ALPN) and h3_client against Google, Cloudflare, Fastly, Akamai, Meta and a few more large origins. Record handshake success, resumption and 0-RTT acceptance, PMTU reached, and body integrity (lengths, and hashes where known). Run it by hand or on a schedule, not on every PR, since it depends on the network.
  2. quic-interop-runner, the standard QUIC interop matrix, with our client and server in its Docker images, against at least ngtcp2, quiche, quic-go, picoquic, msquic and aioquic. Its test cases (handshake, transfer, retry, resumption, zerortt, multiplexing, keyupdate, chacha20, v2, blackhole, and so on) are the credible public evidence for a QUIC stack.

Done when: both runs are documented in H2H3.md with results, and every failure is either fixed or listed as a known limit.

Lingua principale
C
Stelle
0
Fork
0
Merge medio
20h 4m
PR unite (30g)
25

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di public/cursed-http

Tutte le issue di public/cursed-http

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.