The Log Analyzer in Atlassian Troubleshooting and Support tools(ATST) app is not able to reach https://confluence.atlassian.com:443 when Outbound HTTS Proxy credential JVM parameters are defined without the http proxy JVM parameter.

Issue Summary

The Log Analyzer in Atlassian Troubleshooting and Support tools(ATST) app is not able to reach https://confluence.atlassian.com:443 when Outbound HTTS Proxy credential JVM parameters are defined without the http proxy JVM parameter.

This is reproducible on the Data Center: Yes

Steps to Reproduce

• Your proxy server requires authentication and you are using the https proxy credential JVM parameter -Dhttps.proxyUser=<proxy-user> -Dhttps.proxyPassword=<proxy-password> in your Confluence site's Outbound proxy configuration.

Expected Results

The Log analyzer should run without any issues and should be able to download https://confluence.atlassian.com/support/files/179443532/792496589/7882/1696238524754/confluence_regex_v2.xml.

Actual Results

The Log analyzer does not work as it is not sending "Proxy-Authorization: Basic xxxxxxxxx\\r \\n\" when sending a GET call to download https://confluence.atlassian.com/support/files/179443532/792496589/7882/1696238524754/confluence_regex_v2.xml when only https proxy parameters with credentials are defined.

The below exception is thrown in the atlassian-confluence.log file:

2023-10-16 11:47:50,639 WARN [http-nio-8090-exec-239] [troubleshooting.stp.hercules.SupportToolsHerculesScanAction] prepare Log scan failed
 -- referer: https://xxxxxxx/plugins/servlet/troubleshooting/view/ | url: /plugins/servlet/troubleshooting/view/hercules/view | traceId: 0692a85321804aa3 | userName: xxxxxx
java.util.concurrent.ExecutionException: com.thoughtworks.xstream.mapper.CannotResolveClassException: HEAD

Workaround

Add http proxy parameter with credentials using Configuring System Properties.

CATALINA_OPTS="-Dhttp.proxyUser=<proxy-user> -Dhttp.proxyPassword=<Proxy-password> -Dhttp.proxyPort=<proxy-port> -Dhttp.proxyHost=<proxy-host> ${CATALINA_OPTS}"

Note: Adding -Djdk.http.auth.tunneling.disabledSchemes= does not resolve the issue.