[MAGNOLIA-3411] in case of a 302 (not modified) response the gzip filter doesn't make the status transparent Created: 25/Nov/10  Updated: 20/Feb/15  Resolved: 25/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
is causing MAGNOLIA-3413 Fix all the cache filter tests and co... 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   

Due to the changes in MAGNOLIA-3402 is the CacheResponseWrapper not making anything transparent to the original response. This is alright, but the GZipFilter has to ensure that he calls wrappedResponse.replay() if needed.


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