glide.http.proxy_host vs the proxy host in config.xml

[JACQ1]

Hi Everyone,

Does anyone know how the glide.http.proxy_host MID Server property works in relation to the proxy configuration in config.xml?

We recently had an issue with one of our Certificate Discovery integrations. The Discovery failed even though the proxy host was already configured in the MID Server’s config.xml. However, once we added the glide.http.proxy_host value, the Discovery started working.

Does glide.http.proxy_host override the proxy configuration in config.xml, or is it a separate/global proxy setting that applies to HTTP connections from the MID Server?

Thank you

[ayushraj7012933]

hi @JACQ1 
From my understanding, these two settings are not simply an override of one another.

The proxy configured in the MID Server config.xml:

<parameter name="mid.proxy.use_proxy" value="true"/>
<parameter name="mid.proxy.host" value="YOUR_PROXY_HOST"/>
<parameter name="mid.proxy.port" value="YOUR_PROXY_PORT"/>

is the MID Server-level proxy configuration. It controls how the MID Server communicates through the configured proxy. ServiceNow also documents the MID Server proxy configuration using these mid.proxy.* parameters.

glide.http.proxy_host / glide.http.proxy_port, on the other hand, are Platform properties and should not be considered a replacement or direct override for the mid.proxy.* configuration in config.xml.

In your Certificate Discovery case, the fact that adding glide.http.proxy_host made the Discovery work suggests that the particular HTTP request involved in the certificate/integration flow was using the Platform HTTP proxy properties rather than only the MID Server's normal proxy configuration.

So I would look at it as:

MID Server communication/proxy
→ config.xml → mid.proxy.use_proxy, mid.proxy.host, mid.proxy.port

Platform HTTP connection/proxy
→ glide.http.proxy_host, glide.http.proxy_port

Therefore, I wouldn't assume that glide.http.proxy_host overrides the value in config.xml. They can be used for different connection paths.

For troubleshooting, I would also check the MID Server agent0.log around the failed Certificate Discovery and compare the connection that failed with the one that succeeded after adding glide.http.proxy_host. That should help identify which component is actually making the HTTP request.

Also, if the proxy is doing SSL inspection, make sure the MID Server trusts the proxy's certificate/CA. MID Server HTTPS communication performs certificate validation, so a proxy in between can introduce a separate TLS/trust issue.