UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Cadet 3rd Class
Cadet 3rd Class

HTTP/1.1 503 Service Unavailable

I configured proxy in my Application while integrating with Fortify SSC. If I am not enabling proxy everything works fine. I configured proxy on Fortify ssc. Following error is result from Fortify SSC Server:

HttpResponseProxy{HTTP/1.1 503 Service Unavailable [Server: squid/3.5.27, Mime-Version: 1.0, Date: Tue, 10 Mar 2020 18:17:16 GMT, Content-Type: text/html;charset=utf-8, Content-Length: 4157, X-Squid-Error: ERR_DNS_FAIL 0, Vary: Accept-Language, Content-Language: en, X-Cache: MISS from b556a8f038a5, X-Cache-Lookup: MISS from b556a8f038a5:3128, Connection: keep-alive] ResponseEntityProxy{[Content-Type: text/html;charset=utf-8,Content-Length: 4157,Chunked: false]}}

Am I missing something? Do I need to change any configuration setting on Fortify SSC server? 


1 Reply
Micro Focus Expert
Micro Focus Expert

Can you better describe the network topology and where the failure is occurring?

It seems that you are saying that some Application (e.g. Jira) you have connected to your SSC Server can reach the SSC Server URL fine with no Proxy configured, but that when you apply a Proxy setting (Squid proxy) to that Application, then the SSC Server returns a 503 error.  Is that correct?  Could you name the Application in question (and its purpose), and also share the details (or a sanitized copy) of the proxy entry being used?  For the network proxy in question, do you know if it requires user Authentication before it will connect the user through tot he target URL?

The error you posted includes a DNS error.  When a browser/Application is used through this Squid Proxy, where does the Name Resolution occur, on the Proxy or on a DNS Server elsewhere on the network?  Is this the same DNS Server used when you connect from that remote workstation when using no Proxy setting?

Furthermore, there appears to be some known issues with Squid when resolving host names.  Have you checked this with your network team?

SSC Server 19.20 is hosted on Tomcat 9.0.x, defaulting to HTTP on port 8080.  You can customize the port, and enable SSL in Tomcat.  If you have done that, you may need to check that the Proxy can manage the traffic properly.

-- Habeas Data
Micro Focus Fortify Customers-Only Forums – https://community.softwaregrp.com/t5/Fortify/ct-p/fortify
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.