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

Abierto
#57 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C
Estrellas
0
Forks
0
Merge medio
20 h 4 min
PR fusionados (30 d)
25

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de public/cursed-http

Todos los issues de public/cursed-http

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.