You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run HTTP/2 integration tests against local Caddy instead of nghttp2.org (#482)
* Run HTTP/2 integration tests against local Caddy instead of nghttp2.org
The tests hitting nghttp2.org/httpbin/ had been failing on every CI run
because the upstream httpbin backend behind nghttpx returns 502 to
GitHub Actions runners. Enable h2c on the Caddy docker service (via a
new HTTPBIN_H2C_PORT, default 8081, since the existing HTTPBIN_HTTP_PORT
mapping goes directly to httpbin), point the TCP h2c test at it, and
drop the duplicate "nghttp2.org/httpbin" describe block (ping and GET
are already covered by the local "httpbin.org" block).
* Fix stray :ssl message leak in HTTP/2 integration tests
The twitter.com describe block was using @moduletag instead of
@describetag, which made its connect: {"twitter.com", 443} tag apply
to the whole module. That caused the top-level setup to open an HTTPS
connection to twitter.com even for tests outside the describe (like
the TCP h2c test), and the SSL socket's SETTINGS frame would land in
the test mailbox. The previous test had a swallow-hack comment about
"SSL messages sneaking in"; this removes the root cause.
0 commit comments