-
Bug
-
Resolution: Fixed
-
Major
-
4.4
-
None
Most of the responses have now no expiration and caching headers set. This is problematic if a user name or similar is shown after a login. The formally visited pages are then potentially cached on the browser.
Acceptance criteria
- caused by
-
MAGNOLIA-3420 browser cache policy: allow fine grained configuration, better default settings
- Closed