TYPO3 Core

As far as i understand the current implementation, it works like this (simplified):

- The Page Cache Timeout calculation in the TypoScriptFrontendController determines the cache timeout based on the config.cache_period, manual page settings in the backend and (optional) start stop times.
- This value is then used to populate the HTTP header "Cache-Control:max-age=..., if config.sendCacheHeaders is set to 1.

But if i place an TS object on the page with a custom caching configuration, this does not affect the HTTP header sent to the browser (or Varnish in my case).

Example:
lib.dynamicContent = COA
lib.dynamicContent.cache.key = mykey
lib.dynamicContent.cache.lifetime = 3600

I would expect that now the "Cache.Control:max-age" header should be 3600 (-EXEC TIME), but it remains to be the page specific value.

In my opinion this is a must have, otherwise the content specific caching configuration is only of very limited use.