News for hackers. Stuff that matters.

A comment on Chrome is deploying HTTP/3 and IETF QUIC. Parent comment

Re:Chrome is deploying HTTP/3 and IETF QUIC by lostmsu on Wednesday October 07, 2020 @05:40PM (#24713073)
The ad data (text, layout, media) can still be hidden on the client, but AFAIK with QUIC you can push it to the browser regardless if it actually was requested.
[ Parent | on HN ]
Re:Chrome is deploying HTTP/3 and IETF QUIC by slrz on Thursday October 08, 2020 @04:01PM (#24723228)
No. QUIC is a transport protocol. Its purpose is roughly equivalent to TCP: provide a reliable byte stream transport over an unreliable datagram service (IP, though QUIC prepends a small UDP header mostly for compatibility with existing infrastructure).

You might be thinking of the HTTP server push functionality. That was introduced with HTTP/2 and has been deployed for years already over TCP transports (i.e. totally unrelated to QUIC).

Due to how advertising networks work, I'd be surprised if anyone used server push in the way you fear.

[ Parent | on HN ]