Loading Internal Network Resources on the Operator Side via Asset Proxy

This error sometimes occurs in development or staging environments for unspecified protocol.

Glia only uses the proxy when transmission appears to be on HTTP rather than HTTPS, as all communication to the Operator app is an HTTPS web application.  

Oftentimes, in test environments, the protocol does not specify HTTPS, instead using something like “//" to point to the assets in question. This signals to Glia to use the proxy, which won’t work for assets behind your firewall.  

If possible, specify the assets as HTTPS and then Glia will not use the proxy and the assets will not be blocked by your firewall.

Note: This isn’t a problem in production environments as all communication would be outside the firewall, and even if over HTTP, we handle that via the proxy to force to HTTPS.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request