Are there any specific spec'd processes that a browser client can use to dynamically encourage a server to push additional requested items into the browser cache using HTTP/2 server push before the client needs to actually use them (not talking about server-side events or WebSockets, here, btw, but rather HTTP/2 server push)?
相关问题
- POST Base64 encoded data in PHP
- java httpRequest getRemoteAddr allways return 127.
- HttpContent.ReadAsByteArrayAsync() fails without e
- How can I start another request after AbortControl
- High level client for golang http2 server push
相关文章
- Spring WebFlux+Netty 中怎么配置 HTTP/2?
- What is the difference between HTTP parameters and
- Does using image sprites make sense in HTTP/2?
- “Content type 'application/json;charset=UTF-8&
- How to display response in next activity
- Using Httprequest to get pictures from given URL
- Add HEADER in HTTP Request in Java
- Choosing between package:html, dart:html, dart:io
The objective of server push is that the server send additional files (e.g. javascripts, css) along with the requested URL (e.g. an HTML page) to the browser before the browser knows what related files are required, thus saving a round-trip and improve webpage load speed. If the browser already know what resources are needed it can request with normal HTTP calls.
There is nothing (yet) specified formally for browsers to ask a server to push resources.
A browser could figure out what secondary resources needs to render a primary resource, and may send this information to the server opportunistically on a subsequent request with a HTTP header, but as I said, this is not specified yet.
[Disclaimer, I am the Jetty HTTP/2 maintainer] Servers, on the other hand, may learn about resources that browsers ask, and may build a cache of correlated resources that they can push to clients.
Jetty provides a configurable PushCacheFilter that implements the strategy above, and implemented a HTTP/2 Push Demo.