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 detaro on Wednesday October 07, 2020 @08:55PM (#24714564)
HTTP 2 can't just send content from other domains through the same connection (and any proposal that adds the ability, e.g. through signing, also can be used with HTTP 1.1 connections)

And pushed content needs to be accepted by the browser, just sending someone ad bytes doesn't really do anything useful. It doesn't impact adblocking, and if a browser vendor wants to take the adblocking features away they can also just do that for the traditional model.

[ Parent | on HN ]
Re:Chrome is deploying HTTP/3 and IETF QUIC by fiter on Wednesday October 07, 2020 @10:44PM (#24715127)
Ignoring pushed ad data ia very different from never requesting those ads as far as available bandwidth and data metering are concerned.
[ Parent | on HN ]
Re:Chrome is deploying HTTP/3 and IETF QUIC by detaro on Wednesday October 07, 2020 @10:56PM (#24715197)
Clients can refuse pushed requests (e.g. if they match filtering rules), so it's not like the server will push the full files through. It'd be interesting to check if clients do take e.g. OS settings about metering into account and disable push entirely to even avoid the initial transfer.
[ Parent | on HN ]