[MAGNOLIA-1468] SecurityFilter must be before VirtualURIFilter Created: 18/Apr/07 Updated: 23/Jan/13 Resolved: 19/Apr/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 3.0.2 |
| Fix Version/s: | 3.1 M1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Sameer Charles | Assignee: | Sameer Charles |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
Hi Devs, what's the reason that we check security after VirtualURIFilter? this could lead to many security holes, first and obvious would be if you are I would propose to change this order in filter definition, if anyone of you has any concerns please let me know. |