TYPO3 Core

If someone tells me how to patch doc_core_tsref, I will take care of that.

Hi Steffen,

just write down which changes are needed, and where. I'll take care of TSref when the patch is ready.

I forgot: Please send me the text first, I want to post it together with the patch RFC.

Property:
sendCacheHeaders_excludePages

Data type:
integer (page id) /list

Description:
List of pages that should be excluded from cache-control headers (see: sendCacheHeaders). The headers sent for these pages are:
Cache-Control: private
This option makes it possible to prevent client side caching (browser cache, proxy) on certain pages without disabling the page cache.
For example, if you have two pages (e.g. uid 17 and 58) with plugins displaying the content of another sysfolder, changing the content in the sysfolder does not update the timestamp of the those pages. Using cache-control headers, your changes then might be ignored by browsers. The solution is to exclude these pages with:
config.sendCacheHeaders_excludePages = 17,58

Default:

The section is located at page 59 of http://typo3.org/documentation/document-library/references/doc_core_tsref/current/ter_doc_sxw/

Would be a nice feature, but I think for example for tt_news it isn't the right approach, because most news pages are the most requested pages.

I didn't posted an feature request to Rupi yet, but there is the posibilty to set $GLOBALS['TSFE']->register['SYS_LASTCHANGED'] when rendering the news, what would change the cache control headers.

At the moment I use it as a workaround for tt_news, but this does not mean it's the only purpose. Think about webserver logging, which now can be forced for certain pages.

I agree, that this should be handled by the extension, but we have >1000 FE extensions, which probably need better timestamp handling. Outdated SYS_LASTCHANGED fields has never been a big problem , but with cache-control headers, it is. I propose to discussion this in the dev-list.

Maybe we should alter the example in the doc_core_tsref:
Description:
List of pages that should be excluded from cache-control headers (see: sendCacheHeaders). The headers sent for these pages are:
Cache-Control: private
This option makes it possible to prevent client side caching (browser cache, proxy) on certain pages without disabling the page cache.
For example, if you have two pages (with uid 17 and 58) you can exclude these pages with:
config.sendCacheHeaders_excludePages = 17,58

Hi Michael,
will this one make into 4.1?
It's working for me in various installations.

please close.