[MAGNOLIA-5835] Filters that extend from OncePerRequestAbstractMgnlFilter do not get run when there is a request.senderror Created: 17/Jul/14  Updated: 09/Dec/14  Resolved: 02/Dec/14

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 5.2.4, 5.3.1
Fix Version/s: 5.2.9, 5.3.4

Type: Bug Priority: Neutral
Reporter: Teresa Miyar Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MAGNOLIA-5960 OncePerRequestAbstractMgnlFilter must... Closed
relation
is related to MAGNOLIA-6012 Ensure a page defined in 404-section ... 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   

If you have a page defined in the web.xml as the 404 error, it does not get the channel, that is because extends from OncePerRequestAbstractMgnlFilter, and has already been executed, that means that MgnlFilterChain bypasses the filter the second time due an attribute set in the session like "…_FILTERED"
It should probably also check if the response has the and error code


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