test(browser): Chrome, Firefox and WebKit against our HTTP/2 and HTTP/3 servers

Abierto
#58 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c, playwright

Línea de trabajo

Start with H2H3.md and the existing servers-interop target in the Makefile to see how the curl and aioquic interop checks are run. Then read examples/h2_server and examples/h3_server to learn how each is launched and which TLS certificates they use. Done means one repeatable script drives Chrome, Firefox and WebKit through Playwright against both servers, checks each resource's bytes, confirms the negotiated protocol from the browser network log, and is wired into make.

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

Descripción

P0: release blocker

H2H3.md says our servers haven't been tested against browsers yet. Real clients so far are curl (HTTP/2) and aioquic (HTTP/3). Browsers send what synthetic clients don't: bursts of prioritized requests (RFC 9218 and Chrome's own scheme), QPACK with a dynamic table and blocked streams, 0-RTT, GREASE frames, settings and stream types, and connection reuse across origins.

  • Chrome, Firefox and Safari/WebKit loading a page with many subresources from examples/h2_server (TLS) and examples/h3_server, through headless automation (Playwright) on 127.0.0.1, with locally trusted certificates.
  • HTTP/3 forced with --origin-to-force-quic-on in Chrome and the equivalent preferences in Firefox.
  • Check that every resource loads with the right bytes, and that the protocol really was h2 or h3 (from the browser's own network log).

Done when: a repeatable script runs all three browsers against both servers, passes, and is wired into make like servers-interop.

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.