-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
3.5.13, 4.0, 4.3.7
-
Windows 7, FF 6.0.2, Chrome 14.0.835.186
In Firefox and Chrome you can't download a powerpoint file containing special characters in the filename using the view file macro. In my example I attached the file "umlaute_öäüÖÜÄß.pptx" to the page and added this macro:
{viewppt:name=umlaute_öäüÖÜÄß.pptx}. Clicking on the download-link inside the macro works in Internet Explorer 8 and points to this url: https://some.host/download/attachments/12345/umlaute_%C3%B6%C3%A4%C3%BC%C3%96%C3%9C%C3%84%C3%9F.pptx. In FireFox and Chrome however, the link points to https://some.host/download/attachments/12345/umlaute_%F6%E4%FC%D6%DC%C4%DF.pptx and I get a page not found error. So IE uses url-encoding with UTF-8 (which does work) and FireFox & Chrome are using url-encoding with ISO 8859-1, which does not. As a workaround you can download the files directly from the viewpageattachments-page, the download there works fine, even in FireFox & Chrome.
Edit: This is still occurring with later versions of Firefox (up to 29), but no longer in Chrome (at least in version 36).
Workarounds are:
- Rename the file
- Download files from the View Page Attachments page directly
[CONFSERVER-23352] FF & Chrome fail to download ppt-documents via view file macro, if the filename contains special characters, due to encoding problems
No more problems with 5.6.6, seems the issue got solved with some 5.x release. Please update the status of this issue.
Hope this bug will be fixed asap, it's a very basic issue which blocks us...
voted. Still a problem on FF 17.0.11 in Confluence 4.3.7
works fine in Confluence 5.4.4.
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 bugs with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If demand for this picks up, we will reopen the issue.