Details
-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
None
-
-
Empty show more show less
Description
At the moment, the request charset is set using Aggregator.getExtension(), which in turns uses Context.getAttribute. Since the WebContextImpl implementation of getAttribute calls getParameter in case the attribute does not exist on the request, thus making the setCharacterSet call useless - and preventing parameters to be parsed properly (indeed, the container will parse them on the first call to getParam*() with a default encoding - iso-8859-1 in the case of tomcat)
We might solve this by making the Aggregator.getExtension method (and associated) just using the context attribute - which have to be set previously, for instance by a new filter that has yet to be created.
Checklists
Attachments
Issue Links
- depends upon
-
MAGNOLIA-1523 Aggregator can become a simple bean and be exposed in the context
-
- Closed
-
- is depended upon by
-
MGNLFORUM-15 Encoding issue when posting messages
-
- Closed
-