[MAGNOLIA-3310] UnicodeNormalizationFilter seems to be messing up the virtualUriMappings Created: 06/Oct/10 Updated: 20/Feb/15 Resolved: 26/Oct/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 4.3.6 |
| Fix Version/s: | 4.3.8 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Ernst Bunders | Assignee: | Ondrej Chytil |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | vpro | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| 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 |
|
Hello I discovered a problem with a virtual uri mapping (of type forward)and the UnicodeNormalizationFilter. What i try to do is the following: What i want is a virtalUriMapping for this css request, so i can call it without request parameters, making it more cachable. Here is the virtualUriMapping config: this way i can call my css from the template like: http://localhost:8080/pip/themes/1fb8d8e1-d625-4c24-95a3-904e0102eddd/1286288160080/theme.css So that works but oh lala: when the css model class kicks into action: no more request parameters.
All a bit surprising, and It seems to me that the wrapper is still around at the second request handling. Another thing that seems strange: why does the UnicodeNormalizerRequestWrapper has it's own field for the wrapped request and parameters, as it already extends HttpServletRequestWrapper. It seems to me that the only method that actually adds someting is getHeader(String name). And thus: when i switch of the UnicodeNormalization filter: it works! |
| Comments |
| Comment by Jan Haderka [ 11/Oct/10 ] |
|
Thanks for the report. Scheduling for the next maintenance release. |