Pages not displaying properly when Jira Server is integrated with IIS
Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.
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
Problem
When the Jira application is configured to run over an IIS proxy server, the Jira pages might load without the expected styling appearing as seen below:
Note that the login button has moved from the header navigator.
Also, fields on the view issue screen are all jumbled together.
Environment
Jira Server/Data Center on any version
Jira is configured with an IIS Proxy Server
Diagnosis
In Google Chrome, open the development panel.
Go to the Network tab in here and check if you have a Status Code: 400 Bad Request Error for any Atlassian Bundled JavaScripts or CSS files.
In particular, batch.js and batch.css files.
Cause
The maxurllength for the files is longer than is allowed by IIS server for the connected site OR the maximum length of any URL segment (portions of URL between '/'s) is higher than the configured limit in IIS (default is 255)
Resolution
Add the following value to the web.config file of the IIS site you connected to Jira to increase the maxurllength parameter.
1
maxurllength=1024Set the UrlSegmentMaxLength to 1024 if the max URL segment is being exceeded. You can increase the limit in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters\UrlSegmentMaxLength
For more info on IIS HTTP settings, refer to https://support.microsoft.com/en-us/help/820129/http.sys-registry-settings-for-windows
Was this helpful?