Making Chrome QUICer

What happened
Both features have been enabled by default in M131, which was released to Stable on 11/19. This additional DNS resolution introduces latency and significantly reduces the likelihood of connection pooling due to potential IP mismatches.
The journey to optimizing performance did not end when HTTP/3 was default enabled. Recent advancements include the implementation of the HTTP/3 ORIGIN frame ( RFC 9412 ) and Server's Preferred Address ( RFC 9000 Section 9.6 ).
The former enhances connection coalescing, while the latter reduces a connection's round trip time (RTT). ORIGIN Frame When a connection is established for a specific hostname, the server’s certificate typically contains numerous other hostnames for which the server is authoritative.
Key facts
- Both features have been enabled by default in M131, which was — released: to Stable on 11/19
- ORIGIN Frame When a connection is established for a specific hostname, the server’s certificate typically — includes: numerous other hostnames for which the server is authoritative
Sources & evidence
- Chromium Blog Primary / official
Making Chrome QUICer ↗
https://blog.chromium.org/2024/12/making-chrome-quicer.html