After the stale if error period passes the client will receive any error generated The no store request directive allows a client to request that caches refrain from storing the request and corresponding response https://malt-orden.info/userinfo.php?uid=448402 if the origin server s response could be stored The s https://malt-orden.info/userinfo.php?uid=459852 response directive indicates how long the response remains fresh in a shared cache The public response directive indicates that the response can be stored in a shared cache But it s not necessary to revalidate those kinds of static resources even when a user reloads the browser because https://malt-orden.info/userinfo.php?uid=460152 re never modified The stale if error response directive indicates that the cache can reuse a stale response when an upstream server generates an error or when the error is generated https://malt-orden.info/userinfo.php?uid=463585 The React library version will change when you update the library and hero png will also change when you edit the picture For content that s generated dynamically or that s static but updated often you want a user to always receive the most up to date version Typically must revalidate is used with max age Indicates that the response is fresh Note Check the compatibility table for their support user agents that don t recognize them should ignore them must revalidate addresses that Note If index html is controlled under Basic Authentication or Digest Authentication files under assets are not stored in the shared cache This is allowed by the specification because history navigations are usually treated as restoring a snapshot of a historical session and not a new request for a previously visited page Note that no cache means it can be stored but don t reuse before validating so it s not for preventing a response from being stored If assets files are suitable for storing in a shared cache you also need one of public s maxage or must revalidate That s why the example below is equivalent to no cache This usually means the response can be reused for subsequent requests depending on request directives Store a response in caches when the response is cacheable Recently browsers are still using max age 5 in reloading for backward compatibility and alternatively using no cache to cause a force reloading The stale while revalidate response directive indicates that the cache could reuse a stale response while it revalidates it to a cache Responses for requests with Authorization header fields must not be stored in a shared cache however the public directive will cause such responses to be stored in a shared cache Ask the origin server whether or not the stored response is still fresh When you build static assets with versioning hashing mechanisms adding a version hash to https://malt-orden.info/userinfo.php?uid=467304 filename or query string is a good way to manage caching Note that the major browsers do not support requests with min https://malt-orden.info/userinfo.php?uid=461714