Unable to Download Attachments with Space in File Names
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
The content on this page relates to platforms which are not supported. Consequently, Atlassian Support cannot guarantee providing any support for it. Please be aware that this material is provided for your information only and using it is done so at your own risk.
Symptoms
When using IIS as proxy:
Attachments with space in file name can't be downloaded with HTTP 404 Error.
URLs replace spaces with "+".
Cause
This issue is documented in Microsoft's knowledge database as is known as the "URL_DOUBLE_ESCAPED" issue.
Workaround
The following tip may help with IIS configuration:
These steps may change the security level of the server that is running IIS.
Click Start, type Notepad in the Start Search box, right-click Notepad in the Programs list, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type your password, or click Continue.
On the File menu, click Open, type the following in the File name box, and then click Open:
1%windir%\System32\inetsrv\config\applicationHost.configIn the
ApplicationHost.configfile, locate the requestFiltering XML element.Change the value of the allowDoubleEscaping property to True. To do this, use code that resembles the following example code.
1<requestFiltering allowDoubleEscaping="true">On the File menu, click Save.
Resolution
Please see Atlassian's comment on Integration with Third Party Applications and refer to Microsoft's documentation for a fix.
You may also set IIS to allow double escaping for JIRA site only. It can be done in three different ways:
Directly through IIS console as instructed in this documentation;
Or directly modifying the
web.configfile of the IIS Site, inside the<system.webServer>tag, add the following:1 2 3<security> <requestFiltering allowDoubleEscaping="true" /> </security>Or via command line in the IIS server:
1%windir%\system32\inetsrv\appcmd set config "<JIRA_site_name_in_IIS>" -section:system.webServer/security/requestfiltering -allowDoubleEscaping:trueℹ️ It may need to restart JIRA site in IIS.
Was this helpful?