Since CM11, Headless can compute cache-control headers based on content valid from/to dates and a static configuration. Previously, the implementation computed the max-age value based on the content properties valid from/to and and the static configuration based on the request URI.

Unfortunately, even without a configuration for a certain URI, the max-age Cache-Control directive was send, if valid from/to was set for a content that was part of the response.

This changes fixes this behavior. The max-age value is only computed and send, if the request URI matches an existing configuration. Furthermore, the default value for max-age was change from 5 minutes to 2 minutes.

Since the behavior has changed and the default was decreased to two minutes, this change is considered breaking.

If you upgrade from CM10 or older to 2412+, the cache-control header-feature might be considered new and thus non-breaking.

(CMS-26021)