Voting starts in March for the Drupal Association Board election.
In, the CACHE_AGGRESSIVE page cache mode was removed and replaced with the page_cache_invoke_hooks variable that has no UI but should be set in settings.php.
introduced a new variable for controlling the Cache-Control: max-age=x header separate from cache_timeout that is used elsewhere. The new variable may be configured via a select field on admin/config/development/performance. However, this new UI is useless unless the page_cache_invoke_hooks has been set to FALSE in settings.php.
The rationale for sending max-age=0 when page_cache_invoke_hooks is TRUE is that your hook_boot() is (obviously) not invoked, when a page is served from a HTTP proxy without hitting the web server. This made more sense when there were two different caching modes exposed in the UI.
Now that the user can define a the max-age independently from other cache timeouts, it seems reasonable to allow proxy caching even if page_cache_invoke_hooks is TRUE. If the user wants hook_boot() to fire on all page requests, he or she should simply set page_cache_invoke_hooks to 0.
This issue was brought to my attention by jbergstroem.
PASSED: [[SimpleTest]]: [MySQL] 29,900 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 29,912 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 28,783 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 28,815 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 20,426 pass(es). View