-
Bug
-
Resolution: Fixed
-
Neutral
-
3.0.9
Steps to reproduce
- Enable UTF-8 support by setting magnolia.utf8.enabled = true in magnolia.properties.
- Upload an image containing an Umlaut (e.g. ä) in its name to assets. Make sure the Umlaut is non normalised. E.g. ä is encoded as \x61\xCC\x88. (see also info.magnolia.cms.util.UnicodeNormalizer).
- Add the uploaded image to an image component in the pages app.
Expected results
The image displays in the image component.
Actual results
The image is not shown in the image component and a javax.jcr.PathNotFoundException logged.
Development notes
Magnolia normalises URIs to NFC form internally. The assets app however accepts non NFC forms for asset names, which makes such assets inaccessible. (See info.magnolia.cms.filters.UnicodeNormalizationFilter).
Environment
I was able to reproduce this on OSX with Firefox. Other environments might behave differently depending on how file upload deals with encoding of the filename.
Acceptance criteria
- is related to
-
MAGNOLIA-8142 Non ASCII characters in URIs interfere with CsrfTokenSecurityFilter
- Closed