[MAGNOLIA-3402] response headers are added twice: Firefox and Chrome fail to render Created: 25/Nov/10  Updated: 20/Feb/15  Resolved: 01/Dec/10

Status: Closed
Project: Magnolia
Component/s: None
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-2677 Caching big content may cause OutOfMe... Closed
relation
is related to MAGNOLIA-3414 redirects are not working 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   

In MAGNOLIA-2677 I assumed that the CacheResponseWrapper is only recording the response headers, but actually it makes it transparent to the original response.

I will change the CacheResponseWrapper as it allows cleaner code in UseCache and GzipFilter (you know that headers were not yet set and that you can manipulate them).


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