News for hackers. Stuff that matters.
Re:Removing HTTP/2 Server Push from Chrome by jupp0r on Saturday August 20, 2022 @03:59PM (#32534762)
Too many TCP connections is a browser limitation (for DDOS prevention reasons mostly). Inside each connection you are limited by head of line blocking, either by HTTP/1.1 itself or by TCP when using HTTP/2. You are correct that HTTP/3 can stream multiple resources over one QUIC connection via multiple channels and each channel can make progress independently from each other channel. Nowadays (assuming a modern browser in a non-udp restricted environment), you can just download hundreds of resources at the same time from the same server through one HTTP/3 connection without much overhead and transport level limitations.
Re:Removing HTTP/2 Server Push from Chrome by toast0 on Saturday August 20, 2022 @05:54PM (#32535470)
Seems like all the churn could have been avoided by webservers advertising a limit on number of connections and browsers opening up to that limit if needed. Maybe in the connection header, or the keep-alive header, or some new header that Google servers and Chrome Browser could have tried out first.
Re:Removing HTTP/2 Server Push from Chrome by jupp0r on Sunday August 21, 2022 @11:45PM (#32547100)
That doesn’t really solve head of line blocking.