Sourced from github.com/quic-go/quic-go's releases.
v0.43.0
quic-go.net: Launching a new Documentation Site
With this release, we're launching a new documentation site for the quic-go projects (quic-go itself, HTTP/3, webtransport-go, and soon, masque-go): quic-go.net.
The documentation site aims to explain QUIC concepts and how they are made accessible using quic-go's API. This site replaces the wiki, and the ever-growing README files.
A lot of work has gone into the documentation already, but we're by no means done yet. The entire source is public in https://github.com/quic-go/docs/, and we're happy about community contributions.
HTTP Datagrams (RFC 9297)
This release adds support for HTTP Datagrams (RFC 9297), both on the client and on the server side (#4452). HTTP Datagrams are used in WebTransport in CONNECT-UDP (RFC 9298), among others.
The new API for HTTP Datagrams is described on the new documentation page: HTTP Datagrams. The integration of HTTP Datagram support necessitated a comprehensive refactor of the HTTP/3 package, resulting in several breaking API changes listed below.
Breaking Changes
- quicvarint: functions now return an
intinstead the internalprotocol.ByteCount(#4365)- http3:
Server.SetQuicHeaderswas renamed toSetQUICHeaders(#4377)- http3:
Server.QuicConfigwas renamed toQUICConfig(#4384)- http3:
RoundTripper.QuicConfigwas renamed toQUICConfig(#4385)- http3:
RoundTripOpt.CheckSettingswas removed (#4416). Use the newSingleDestinationRoundTripperAPI instead.- http3: the
HTTPStreamerinterface is now implemented by thehttp.ResponseWriter(and not thehttp.Request.Body) (#4469)- include the maximum payload size in the
DatagramTooLargeError(#4470)Other Notable Changes
- GSO and ECN is disabled on kernel versions older than 5 (#4456)
- http3: logging can be controlled using an
slog.Logger(#4449)- http3: HEAD requests can now be sent in 0-RTT (#4378)
- http3: duplicate QPACK encoder and decoder streams are not rejected as required by the RFC (#4388)
- http3: Extended CONNECT are blocked until the server's SETTINGS are received, as required by the RFC (#4450)
- http3: HTTP/3 client connections aren't removed if
RoundTriperrors due to a cancelled context (#4448). Thanks to@GeorgeMac!- http3: sniff Content-Type when flushing the ResponseWriter (#4412). Thanks to
@WeidiDeng!- The
Contextexposed on thequic.Streamis now derived from the connection's context (#4414)- The UDP send and receive buffer size was increased to 7 MiB (#4455). Thanks to
@bt90!Clarifications on the QUIC Stream State Machine
Calling CancelWrite after Close
After a long and fruitful discussion (#4404), we decided to clarify that calling
CancelWriteafterCloseon aSendStream(or a bidirectional stream) should cause a state transition from the "Data Sent" to the "Reset Sent" state, as described in section 3.1 of RFC 9000. This matches the current behavior of quic-go, however, it didn't match the API documentation (fixed in #4419).This means that stream data will not be delivered reliably if
CancelWriteis called, and that this applies even ifClosewas called before.Garbage Collection of Streams
This release also changes the way streams are garbage-collected (and the peer is granted additional limit to open a new stream), once they're not needed anymore, in a subtle way:
- for the send direction of streams: #4445
... (truncated)
93c4785
http3: sniff Content-Type when flushing the ResponseWriter (#4412)c0250ce
include the maximum payload size in the DatagramTooLargeError (#4470)34f4d14
http3: implement on the HTTPStreamer on the ResponseWriter, flush header
(#4469)083ceb4
http3: rename Settings.EnableDatagram to EnableDatagrams (#4466)e1e5b62
README: link to the new documentation site (#4464)2a37c53
http3: add support for HTTP Datagrams (RFC 9297) (#4452)11b1159
http3: fix race condition in client unit test (#4463)4b87539
delay completion of the receive stream until the reset error was read
(#4460)bff131e
delay completion of the send stream until the reset error was delivered
(#4445)12aa638
disable GSO and ECN on kernels older than version 5 (#4456)