Nnnnie pdf cache-control max-stale

The basic cachecontrol header defines amount of time that a file should be cached and the manner in which that caching should take place. When the cachecontrol header is included the browser will respect the values found there. The cache control generalheader field is used to specify directives for caching mechanisms in both requests and responses. The cache control header can contain the following values. If max stale is assigned a value, then the client is willing to accept a response that has exceeded its freshness lifetime by no more than the specified number of seconds. This directive overrides the maxage directive and expires header. In this in this manual the generic term cache controller means the pl310 cache controller. Overrides maxage or the expires header, but it only applies to shared caches e. Caching directives are unidirectional, meaning that a given directive in a request is not implying that the same directive is to be given in the response. The value of this header determines whether cached portlet content can be shared among different users. I believe shahkalpeshs answer applies to the user agent side. Returns the value of the cachecontrol header maxage.

This setting means that, if a request for the time is repeated within the next 1 second, the previously cached value will still be fresh, and used asis, without any revalidation. For example, maxage, maxstale, and minfresh do what they sound like. That is, max age is the oldest that a response can be, as long as the cache control from the origin server indicates that it is still fresh. Cache control max age3600, mustrevalidate it is telling both client caches and proxy caches that once the content is stale older than 3600 seconds they must revalidate at the origin server before they can serve the content. The cache control header can be used to expire content immediately or disable caching altogether. Returns the value of the cachecontrol header maxstale. Overrides maxage or the expires header, but only for shared caches e. In short, stale assets must first be verified and expired assets should not be used. That is, maxage is the oldest that a response can be, as long as the cachecontrol from the origin server indicates that it is still fresh.

771 1512 279 1074 1202 1460 148 1398 740 108 1008 290 265 419 480 1290 605 1043 1495 708 705 704 489 1507 901 388 844 1207 784 156 789 1027 237 1414 150 973 994 467