Re:Removing HTTP/2 Server Push from Chrome
by jefftk on Friday August 19, 2022 @01:02PM
(#32523528)
That's the idea that led to implementing server push. Lots of people it, and it turns out not to work very well. There's too much variation in what people will already have in their caches and the server is not great at predicting the order in which clients will need the resources.
[ Parent
| on HN ]
Re:Removing HTTP/2 Server Push from Chrome
by vbezhenar on Friday August 19, 2022 @02:13PM
(#32524363)
Client can send bloom filter with first request.
Re:Removing HTTP/2 Server Push from Chrome
by habibur on Friday August 19, 2022 @02:50PM
(#32524721)
How? The client needs to know what the resources are to create a bloom filter. It doesn't know that before 1st request.
Re:Removing HTTP/2 Server Push from Chrome
by vbezhenar on Friday August 19, 2022 @05:02PM
(#32525865)
First request is empty filter, server will push everything mentioned in HTML. For subsequent requests browser will fill filter with known hashes, server will push changed resources (and false positives).
Re:Removing HTTP/2 Server Push from Chrome
by mort96 on Saturday August 20, 2022 @04:33AM
(#32530389)
But for subsequent requests the content is cached.
your browser can have a bloom filter for each subdomain.
I'm just still shocked that this wasn't obvious to more people before: it isn't like you even need to have implemented this feature to do the instrumentation required to know whether this would work, and it frankly had always seemed like a long shot.