Jira server ignores http.nonProxyHosts JVM option
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.
When a JIRA application is configured to use an outbound proxy with the
-Dhttp.proxyHost JVM argument, Crowd or other service integrations are not bypassing the proxy and connection fails. This occurs even if
-Dhttp.nonProxyHosts appears to be appropriately set.
In Windows environment, JIRA can't start if a pipe character ( | ) is used for
-Dhttp.nonProxyHosts in setenv.bat.
There are a few causes for this issue:
(Unix/Linux only): The pipe character ( | ) may require backslash ( \ ) escaping so it is not translated as a shell pipeline:
(Windows only): The pipe character ( | ) can't be escaped using ( ^ ) and the host following it is not recognized as an internal or external command, operable program or batch file.
The value should not be both quoted and escaped. For example, this does not work as the backslash character is passed in as part of the value:
(JIRA version < 4.3 only): Your JIRA application's lib directory includes
xfire-core-1.2.6.jar, but both of those jar files don't include the
transport.http.ProxyUtilsclass, the controller of the JVM proxy options. This defect JRA-20715 was fixed in JIRA 4.3.
Due to issues with escaping,
-Dhttp.nonProxyHostsshouldn't be defined in setenv.bat or setenv.sh. Instead, set it in <
- Ensure there are no quotation marks in the value.
If you are using JIRA 4.3 or earlier: