tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity
c7fb61120e
silverstripe-framework/docs/en/howto/cache-control.md
Ingo Schommer 3334eafcb1 API Marked statics private, use Config API instead (#8317) 
See "Static configuration properties are now immutable, you must use Config API." in the 3.1 change log for details.
2013-03-24 17:20:53 +01:00

1.4 KiB
Raw Blame History

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

  • [api:HTTP::$cache_age] 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.
  • [api:HTTP::register_modification_date()] can be used to set the modification date to something more recent than the default.

How it works:

  • [api:DataObject::__construct()] calls [api:HTTP::register_modification_date()] whenever a record comes from the database
  • Controller::run() calls [api:HTTP::add_cache_headers()] before outputting the page