3483221 - Understanding the HEAD Request Sent from Cloud Connector to Proxy

In the SAP Cloud Connector trace (ljs_trace.log / scc_core.trc), following HEAD request is being sent to the proxy. The log entries might look like this:

====
2024-05-30 13:52:38,991 +0000#DEBUG#org.apache.http.headers#https-jsse-nio2-8443-exec-6#          #http-outgoing-18 >> HEAD / HTTP/1.1
2024-05-30 13:52:38,991 +0000#DEBUG#org.apache.http.headers#https-jsse-nio2-8443-exec-6#          #http-outgoing-18 >> Host: <PROXY HOST>:<PORT>
2024-05-30 13:52:38,991 +0000#DEBUG#org.apache.http.headers#https-jsse-nio2-8443-exec-6#          #http-outgoing-18 >> Connection: Keep-Alive
2024-05-30 13:52:38,991 +0000#DEBUG#org.apache.http.headers#https-jsse-nio2-8443-exec-6#          #http-outgoing-18 >> User-Agent: Apache-HttpClient/4.5.14 (Java/1.8.0_401)
2024-05-30 13:52:38,991 +0000#DEBUG#org.apache.http.headers#https-jsse-nio2-8443-exec-6#          #http-outgoing-18 >> Accept-Encoding: gzip,deflate
====

SAP Cloud Connector(SCC) release independent

sap cloud connector, scc, cc, connector, proxy, proxy server, HEAD, proxy host, proxy port, SCC UI, web ui, SCC web UI, connection, HTTPS, HTTPS proxy, 3128, 8080, squid, squid proxy, org.apache.http.headers , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , Problem