[MAGNOLIA-1219] Cache filter does not set last modified date in response Created: 17/Nov/06  Updated: 20/Nov/06  Resolved: 17/Nov/06

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

Type: Bug Priority: Minor
Reporter: Sameer Charles Assignee: Sameer Charles
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MAGNOLIA-1216 Cache: Modification-Date is not set -... 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   

Since cache is moved to a filter it does not set response headers properly.
most important is to set last modified header to allow broser and proxy cache



 Comments   
Comment by Philipp Bracher [ 17/Nov/06 ]

MAGNOLIA-1216

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