-
Bug
-
Resolution: Workaround exists
-
Major
-
None
-
None
-
None
-
-
Empty show more show less
A workaround would be to use the POST form method, but that's not exactly satisfying.
Managing the encoding in the model could also work, but I really think it should be solvable at template/form/container level.
There was an issue before with the old Magnolia samples where we found out quite a few things about this, can't find it right now.
Acceptance criteria
- is related to
-
MAGNOLIA-2835 Configure bundled Tomcat to use UTF-8 for uriEncoding
- Closed
-
MGNLEE-154 Configure bundled Tomcat to use UTF-8 for uriEncoding
- Closed