CacheHeaders
[Page]
Introduces different cache header policies than the core. More...
Classes |
|
| class | CacheHeadersPageView |
| An overloaded PageView to serve other cache
headers. More... |
|
| class | ConfigCacheHeaders |
| CacheHeaders config options. More... |
|
| class | ViewFactoryCacheHeaders |
| Overload View Factory to create PageViews
with overloaded cache headers. More... |
|
Detailed Description
Introduces different cache header policies than the core.
The core default caching headers allow the browser to keep local caches of pages without checking back for changes for about 10% of local cache duration time. That is: If a page is stored in local cache for ten hours, the browser won't check for the freshness of that page for one hour after fetching it.
This usually is fine, if pages don't change to much. If however your page is highly dynamic, like a forum, it's usually better to force the browser to check the freshness of a page on each request. While this extends the number of requests, it let's your users see always the latest content. If the content has not changed, the browser of course still will get a "304 - Not Modified" response.