Try the beta version of the new SilverStripe documentation

For the next 2 weeks you can use the new documentation website and give us your feedback.

close

This document contains information for an outdated version (2.3) and may not be maintained any more.

If some of your projects still use this version, consider upgrading as soon as possible.

Cache control

By default, PHP add caching headers that make the page appear "purely dynamic".
This isn't usually appropriate for most sites, even ones that are updated reasonably frequently.
In particular, the default PHP cache-control settings prevent sites from appearing in the internet archive.
SilverStripe overrides the default settings with the following:

Default setting:

  • The Last-Modified date is set to be most recent modification date of any database record queried in the generation of the page.
  • The Expiry date is set by taking the age of the page and adding that to the current time.
  • Cache-Control is set to max-age=86400, must-revalidate
  • Since a visitor cookie is set, the site won't be cached by proxies
  • Ajax requests are never cached.

Overriding these defaults

  • HTTP::set_cache_age()&version=2.3&module=framework) can be used to set the max-age component of the cache-control line, in seconds.
    Set it to 0 to disable caching; the "no-cache" clause in Cache-Control and Pragma will be included.
  • HTTP::register_modification_date()&version=2.3&module=framework) can be used to set the modification date to something more recent than the default.

How it works:

Comments

Comment policy: Please use comments for tips and corrections about the described functionality.
Comments are moderated, we reserve the right to remove comments that are inappropriate or are no longer relevant. Use the Silverstripe Forum to ask questions.

blog comments powered by Disqus