[MGNLDATA-119] Tree with utf8 characters in its name can't be resolved properly Created: 24/Jan/11 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia Data Module (closed) |
| Component/s: | None |
| Affects Version/s: | 1.4.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Zdenek Skodik | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
and throws the InvalidTreeHandlerException as attached. To reproduce:
|
| Comments |
| Comment by Federico Grilli [ 24/Jan/11 ] |
|
the UnicodeNormalizationFilter seems to do its job and wraps the request with info.magnolia.cms.filters.UnicodeNormalizationRequestWrapper but then in info.magnolia.module.admininterface.AdminTreeMVCServlet.getHandler(HttpServletRequest, HttpServletResponse) the call to String handlerName = request.getRequestURI();
returns the encoded URI instead of the normalized one. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |