[MAGNOLIA-2178] Error pages are sent with gzip headers Created: 09/Jun/08  Updated: 23/Jan/13  Resolved: 14/Jul/08

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

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2177 When caching (1st request), we're alw... Closed
is related to MAGNOLIA-2129 Cache : RenderingFilter should not fl... Closed
is related to MAGNOLIA-2936 Error pages not served properly Closed
is related to MAGNOLIA-2968 security: login form fails to render ... 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   

Similarly to MAGNOLIA-2177, when an error page is served, we still serve it with the headers added by the gzip filter. Firefox displays this as a blank page. Further requests to the same uri are served through the cache, and CachedError only sets the error code, so these work fine.



 Comments   
Comment by Magnolia International [ 14/Jul/08 ]

Note that when the cache is disabled or bypassed, the error pages are then always served with gzip header, and neither Safari 3 (NSURLErrorDomain:-1015) nor Firefox 3 ("the page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression") renders them properly.

Comment by Magnolia International [ 14/Jul/08 ]

currently solved by preventing further filters from flushing the response, which allows the GZipFilter to set its headers after other filters have done their business, when we can determine if we're serving a 200 response.

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