You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 3, 2023. It is now read-only.
There is an inconsistency with the cache key generation and usage. When a page is generated for the page cache, FrontendTemplate::addToCachealways uses the current host for the cache key: system/modules/core/classes/FrontendTemplate.php#L216-L220
But the cache file was generated with example.org/empty.de as its cache key.
This then leads to the start page never being served from the page cache, if the internal cache is built and no DNS setting was present in the website root.
The text was updated successfully, but these errors were encountered:
There is an inconsistency with the cache key generation and usage. When a page is generated for the page cache,
FrontendTemplate::addToCache
always uses the current host for the cache key:system/modules/core/classes/FrontendTemplate.php#L216-L220
However,
Automator::generateConfigCache
always uses either the DNS setting from the page object or*
:system/modules/core/library/Contao/Automator.php#L539
So when the internal cache is active, the resulting
system/cache/config/mapping.php
will look like this for example:But the cache file was generated with
example.org/empty.de
as its cache key.This then leads to the start page never being served from the page cache, if the internal cache is built and no DNS setting was present in the website root.
The text was updated successfully, but these errors were encountered: