Rules of Thumb for HTTP/2 Push

Re:Rules of Thumb for HTTP/2 Push by vbezhenar on Thursday August 04, 2016 @08:09AM (#12224948)

I have very fast mobile internet (4G, so I can download megabytes of traffic in one second) yet this traffic might cost a lot. And my pings to US server might easily be second or more. So basically I risk to download an entire website which is already in the my cache for each HTTP request.

Honestly I'm not sure that I like this server push. I think, the only appropriate use is: server push if client misses some cookie and set this cookie immediately.

[ Parent | on HN ]

Re:Rules of Thumb for HTTP/2 Push by Lukasa on Thursday August 04, 2016 @08:24AM (#12225003)

We're working on a draft that will allow clients to signal what resources are already in their cache. This should allow us to reduce the bandwidth risk of unnecessary pushes.

[ Parent | on HN ]

Re:Rules of Thumb for HTTP/2 Push by theandrewbailey on Thursday August 04, 2016 @12:50PM (#12226828)

What about a header to tell the server to not push anything?

[ Parent | on HN ]

Re:Rules of Thumb for HTTP/2 Push by ropiku on Thursday August 04, 2016 @07:18PM (#12229130)

Clients can always disable push using SETTINGS_ENABLE_PUSH. They can also reject each pushed resource (stream) https://daveyshafik.com/archives/69603-http2-server-push-you...

[ Parent | on HN ]