-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 8.2, 9.10
-
Component/s: Azure
-
Release Notes Summary:Files whose name contains special characters are successfully downloaded from Azure.
-
Tags:
-
Backlog priority:800
-
Sprint:nxFG 10.10.4
When the Azure BlobManager is configured to use direct download from the Azure CDN, the nxfile servlet is redirecting to the wrong URL when the filename contains spaces, causing the file to not be downloadable. This does not happen with filenames that do not contain spaces.
Example of how to emulate:
- upload a file with the name "Hey this is some fake stuff for a fake word document.docx"
- try to download the file in the Nuxeo UI
- Nuxeo nxfile gives a HTTP 302 redirect with the url http://<_some azure url>&rscd=attachment%3B%20filename%3DHey%20this%20is% 20some%20fake%20stuff%20for%20a%20fake%20word%20document.docx&sp=r&sr=b (spaces are encoded as %20)
- Nuxeo then tries to do a redirect to http://<some azure url>&rscd=attachment%3B%2520filename%3DHey%2520this%2520is% 20some%2520fake%2520stuff%2520for%2520a%2520fake%2520word%2520document.docx&sp=r&sr=b (the %20 is now encoded as %2520)
If we manually change the %2520 to %20 in the URL, the file is downloadable.