The configuration for the blobcache of headless-server was missing. Therefore defaults were used.

While the default should work in a non containerized environment, for example, a Docker environment requires a dedicated configuration using volumes. Otherwise performance may suffer. Additionally the config of headless-server in preview and live mode should point to different locations.

As this is a change in the deployment configuration, this change is considered breaking. Customers who use headless-server should check their configuration on deployment level and eventually update or adopt the setting to their needs.

(CMS-17111)