Intent to Remove: HTTP/2 and gQUIC server push

BRANK

Primary eng (and PM) emailslas...@chromium.org,dsch...@chromium.org,b...@chromium.org,ians...@chromium.orgSummaryRemove the ability to receive, keep in memory, and use HTTP/2 and gQUIC push streams sent by the server.  Send SETTINGS_ENABLE_PUSH = 0 at the beginning of every HTTP/2 and gQUIC connection to request that servers not send them.BackgroundHTTP/2 allows servers to “push” a resource that the client will likely need before the client actually requests it, see  The specification allows the client to reject the pushed resource at its discretion.gQUIC is a non-standard protocol supported by Google servers, Akamai, and Litespeed.  It also allows servers to push resources in a fashion very similar to HTTP/2.  gQUIC is being obsoleted by HTTP/3 and support will eventually be removed entirely.HTTP/3 is an almost-RFC protocol that also defines server push, see currently supports handling push streams over HTTP/2 and gQUIC, and this intent is about removing support over both protocol…