If there's a match, the response is read from the cache, which eliminates both the network latency and the data costs that the transfer incurs. Last-Modified How the HTTP Cache works #Īll HTTP requests that the browser makes are first routed to the browser cache to check whether there is a valid cached response that can be used to fulfill the request.Those APIs are supported in all browsers: It's the general name for a collection of web platform APIs. There isn't actually a single API called the HTTP Cache. This guide shows you the basics of an effective HTTP caching implementation. It's not necessarily the most powerful or flexible approach, and you have limited control over the lifetime of cached responses, but it's effective, it's supported in all browsers, and it doesn't require much work. How can you avoid unnecessary network requests? The browser's HTTP Cache is your first line of defense. If a person is accessing your site with a limited mobile data plan, every unnecessary network request is a waste of their money.Your page won't load until all of its critical resources have downloaded completely.Large responses require many roundtrips between the browser and the server.Server revalidation for unversioned URLsįetching resources over the network is both slow and expensive:.Which response header values should you use?.Response headers: configure your web server.Request headers: stick with the defaults (usually).
0 kommentar(er)
