Details
-
Improvement
-
Resolution: Unresolved
-
Neutral
-
None
-
5.7.5
-
None
-
None
Description
It would be good to preserve cache-control headers when redirecting to error pages. This way it would be possible to take load off Magnolia by caching error-pages (404..)
Detailed requirements from SUPPORT-10809 are:
- Retain original response headers in case of sendError, or
- Make sure we can set Custom Response Headers in case of sendError (404, 500, etc) which are then used with a custom error page
- (side but related topic) ensure that status code is retained across request (-> in the ContentTypeFilter, the StatusSniffingResponseWrapper always sets this status to 200 even when it's a 404!!)
- ensure that Cache Voters (browserCachePolicy & cachePolicies) are executed for 404 requests so that they can properly vote for TTLs
Checklists
Acceptance criteria