<story><title>RFC 9114 – HTTP/3</title><url>https://www.rfc-editor.org/info/rfc9114</url></story><parent_chain></parent_chain><comment><author>nateberkopec</author><text>Why does HTTP3 still support server push? When Chrome dropped it from their HTTP&amp;#x2F;2 implementation, I thought it was dead.&lt;p&gt;Cloudflare has also said they’re not implementing server push in their HTTP&amp;#x2F;3 support and will instead encourage Early Hints.</text></comment>
<story><title>RFC 9114 – HTTP/3</title><url>https://www.rfc-editor.org/info/rfc9114</url></story><parent_chain></parent_chain><comment><author>akshayshah</author><text>This is great! Despite how little the draft has changed over the last year, many communities seemed reluctant to work on an implementation until the RFC was published. Go definitely fell into this camp. Kudos to .NET for shipping HTTP&amp;#x2F;3 support in Kestrel already!&lt;p&gt;I have to say that I&amp;#x27;m most excited for RFC 9110 (HTTP semantics), though :)</text></comment>