[MAGNOLIA-2046] Wrong filter configuration completely breaks Magnolia Created: 06/Feb/08  Updated: 02/Dec/13  Resolved: 06/Aug/08

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.5.4
Fix Version/s: 3.6.2, 3.6.3

Type: Task Priority: Critical
Reporter: Vivian Steller Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File clipboard.txt    
Issue Links:
duplicate
is duplicated by MAGNOLIA-2261 Magnolia access failure whit miss-con... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

If you accidentally configure the filter chain wrongly in Magnolia you can easily break the complete instance and prevent it from starting up again.

E.g. consider the following scenario:
1. Start (an already installed) Magnolia instance
2. add a bypass configuration on the Main Magnolia Filter (/server/filters) node
3. add property class=info.magnolia.voting.voters.URIStartsWithVoter
now, when adding the property "pattern" you'll get a 500 when hitting enter due to a Null exception. This happens since Content2Bean is not able to initialize the filter chain again.

See the exception attached.



 Comments   
Comment by Magnolia International [ 07/Feb/08 ]

This is also the case for i18nSupport !

Comment by Jan Haderka [ 06/Aug/08 ]

r17219

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