This article explains how to perform a connectivity test from the Edge SWG (ProxySG) CLI by sending an HTTP GET request to an Origin Content Server (OCS). A successful HTTP GET request should result in HTTP code 200 or HTTP code 302 (redirection) indicating of successful connections from Edge SWG (ProxySG) to OCS. Other codes, for example: 401 unauthorized, or 502 bad gateway, may indicate deployment or configuration issues.
Note: Some websites operate only HTTPS, so you should expect to receive an HTTP response code 302 for redirection when testing with such a site.
To perform the test, SSH into the Edge SWG (ProxySG) CLI and issue the following command: test http get www.mycompany.com
Note the HTTP GET results on the last line in the output.
The HTTP response code 302, redirecting the URL to https://www.mycompany.com
Optionally, you can also view this and other tests with a packet capture. You can refer to the following article: How do I create a packet capture filter to capture HTTP GET requests?
For help setting up a packet capture on Edge SWG (ProxySG), refer to article: Using packet captures - Quick start guide on how to run packet capture from CLI.