Documentation for JIRA 4.1. Documentation for other versions of JIRA is available too.

In most cases URLs running over HTTP work fine, but not when using HTTPS (i.e. over SSL). JIRA is running in Tomcat (or JIRA Standalone). This usually results in Unicode (non-ASCII) characters in an HTTPS URL appear incorrect in the URL, and the served page contains numerous errors

This occurs when the useBodyEncodingForURI="true" flag is not defined in the HTTPS connector definition in JIRA_HOME/conf/server.xml. Ensure that the useBodyEncodingForURI="true" flag is included in the section for HTTPS:

            <Connector port="8443" maxHttpHeaderSize="8192"
              maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
              enableLookups="false" disableUploadTimeout="true"
              acceptCount="100" scheme="https" secure="true"
              clientAuth="false" sslProtocol="TLS" useBodyEncodingForURI="true" />

After specifying the useBodyEncodingForURI="true" in all connector definitions (i.e. both the HTTP and the HTTPS connectors), as described in the Modifying Tomcat server.xml documentation.

Unknown macro: {htmlcomment}

Severity: Low
Regular Expression: characters in an HTTPS URL appear incorrect in the URL
Article ID: JIRAKB223220048

http://support.atlassian.com/browse/JSP-27758



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.