* feat: cache alt-svc headers and announce all listeners instead of just one
* feat: use Server.Addr for SetQuicHeaders if no port is available from listeners
* feat(http3): implement serving from quic.Listener
ServeListener method added to http3.Server allowing serving from an existing listener
ConfigureTLSConfig function added to http3 which should be used to create listeners meant for serving http3.
* docs(http3): add note about using ConfigureTLSConfig to ServeListener
* fix(http3): stop serving non-created listeners after Server.Close
* refactor(http3): return ErrServerClosed once server closes instead of context.Canceled
* feat(http3): close listeners from ServeListener as well
* fix(http3): fix logger not being setup during ServeListener
* test(http3): add unit tests for serving listeners
* test(http3): add tests for ConfigureTLSConfig
* test(http3): added server hotswapping integration test
* fix: race condition in listener tests
Currently, it's not possible to send informational responses such as 103 Early Hints or 102 Processing.
This patch allows calling WriteHeader() multiple times in order to send informational responses before the final one.
It follows the patch for HTTP/1 (golang/go#42597) and HTTP/2 (golang/net#96).
In conformance with RFC 8297, if the status code is 103 the current content of the header map is also sent. Its content is not removed after the call to WriteHeader() because the headers must also be included in the final response.
The Chrome and Fastly teams are starting a large-scale experiment to measure the real-life impact of the 103 status code.
Using Early Hints is proposed as a (partial) alternative to Server Push, which are going to be removed from Chrome: https://groups.google.com/a/chromium.org/g/blink-dev/c/K3rYLvmQUBY/m/21anpFhxAQAJ
Being able to send this status code from servers implemented using Go would help to see if implementing it in browsers is worth it.
We don't need these streams, since our QPACK implementation doesn't use the
dynamic table yet. However, we MUST NOT close / reset these streams. Instead,
just ignore them.
Otherwise, we'll only be able to issue https requests. This is what we
usually want, but for MASQUE support, the URL will be of the form
masque://example.org.
