[MAGNOLIA-3426] New browser cache configuration is too lax Created: 30/Nov/10  Updated: 20/Feb/15  Resolved: 30/Nov/10

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 4.4
Fix Version/s: 4.4

Type: Bug Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-3420 browser cache policy: allow fine grai... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

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.



 Comments   
Comment by Philipp Bärfuss [ 30/Nov/10 ]

The new configuration was introduced in MAGNOLIA-3420.

Generated at Mon Feb 12 03:46:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.