[MAGNOLIA-1745] Bypass on top filter node has no effect Created: 20/Sep/07  Updated: 23/Jan/13  Resolved: 18/Oct/07

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.1 M3
Fix Version/s: 3.5 RC1

Type: Bug Priority: Blocker
Reporter: Sameer Charles Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MAGNOLIA-1693 bypasses at the top level does not work 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   

Bypass node at the top level is simply ignored, if we need to bypass multiple URI we actually have to configure this to each filter
bypass and if a new filter is added by any module or core we are again screwed.



 Comments   
Comment by Philipp Bracher [ 12/Oct/07 ]

I will separate the MainFilter (registered in web.xml) and the root filter defined in /server/filters. This will simplify the code and facilitate the usage of content2bean.

In addition I will rename/deprectate the filters so that we have a more consistent naming. So please commit all changes related to filters in your local copies or you will hate me

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