[MAGNOLIA-1216] Cache: Modification-Date is not set --> browser cache is not working Created: 16/Nov/06  Updated: 23/Jan/13  Resolved: 05/Dec/06

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.0 Final
Fix Version/s: 3.0.1

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

Issue Links:
duplicate
is duplicated by MAGNOLIA-1219 Cache filter does not set last modifi... 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
Date of First Response:

 Description   

In 2.1 we set the modification date by implementing the servlets method getModificationDate(). Unfortunatelly we forgot to move this method to the filters.

We should handlse this in the Cache filter



 Comments   
Comment by Marco Struck [ 17/Nov/06 ]

I'm not shure whether the cache filter is the right place for that.

Does it work then, when the cache is disabled?

Comment by Sameer Charles [ 04/Dec/06 ]

No it does not work if cache is disabled, CMSFilter does not set modification time either.
Both cms and cache filters work on different data sources, we need to handle it separately for these filters.

Comment by Sameer Charles [ 05/Dec/06 ]

fixed

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