Re:Removing HTTP/2 Server Push from Chrome
by Matthias247 on Friday August 19, 2022 @07:00PM
(#32527092)
Even if a client does a RST_STREAM, the origin server might already have done a lot of additional work (e.g. request the pushed file from an upstream if it's a proxy/CDN), and probably stuffed min(TCP_SEND_BUFFER_SIZE, STREAM_FLOW_CONTRO_WINDOW) of data into the stream. Which then also means all of that work might get billed if the server is a managed service. It's really quite some waste of resources compared to the client sending an additional request (which might even be a conditional request).
[ Parent
| on HN ]
Re:Removing HTTP/2 Server Push from Chrome
by coder543 on Friday August 19, 2022 @07:02PM
(#32527120)
Yeah, and unless I’m wrong, this also means the TTFB could be significantly higher, since I think the PUSH_PROMISE frames need to come before the main content. Doing that at least requires gathering up the information on those objects, which takes time.
you are 100% right :-(
The spec say
"The server SHOULD send PUSH_PROMISE (Section 6.6) frames prior to sending any frames that reference the promised responses. This avoids a race where clients issue requests prior to receiving any PUSH_PROMISE frames."
Re:Removing HTTP/2 Server Push from Chrome
by Matthias247 on Friday August 19, 2022 @08:52PM
(#32527919)
even if a server implements that behavior, it could however just send the PUSH_PROMISE frame (containing HTTP headers) but doesn't have to send the associated data frames yet. The frames associated with the original response could follow earlier.