The role of HTTP cache
HTTP is typically used for distributed information systems, where performance can be improved by the use of response caches.
The response header is not configured with cache
In the following cases, the browser will not cache the request
No cache control, last modified or expired is configured
Only cache control is configured, and the value is public or private
Only last modified is configured
- Expires is not configured
- not configured
- Or configuration, the value is public or private
Heuristic expiration will be used
Since origin servers do not always provide explicit expiration times, HTTP caches typically assign heuristic expiration times, employing algorithms that use other header values (such as the Last-Modified time) to estimate a plausible expiration time. The HTTP/1.1 specification does not provide specific algorithms, but does impose worst-case constraints on their results. Since heuristic expiration times might compromise semantic transparency, they ought to used cautiously, and we encourage origin servers to provide explicit expiration times as much as possible.
Is it really effective to control the cache by setting expires and cache control in HTML meta?
- service work