Perform HTTP GET request from Edge SWG (ProxySG) Command Line Interface

Products

• ProxySG Software - SGOS

Issue/Introduction

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, HTTP code 302 (redirection), or HTTP code 301 (Moved Permanently) indicating successful connections from the Edge SWG (ProxySG) to OCS.

Other HTTP response codes may indicate deployment or configuration issues, such as 401 unauthorized, or 502 bad gateway.

Some websites operate only HTTPS. An HTTP request to such a site will redirect result in an HTTP response code 302 for redirection to the secure site.


 

Resolution

To perform the test, SSH into the Edge SWG (ProxySG) CLI and issue the following command:

x.x.x.x - Blue Coat SG-VA Series#test http get www.example.com

Type escape sequence to abort.
Executing HTTP get test

* HTTP request header sent:
GET HTTP://www.example.com/ HTTP/1.0
Host: www.example.com
User-Agent: HTTP_TEST_CLIENT

* HTTP response header recv'd:
HTTP/1.1 301 Moved Permanently
...
Access-Control-Allow-Headers: x-requested-with, accept-encoding, cache-control, origin, accept-language, content-type
Access-Control-Allow-Methods: GET, OPTIONS
Access-Control-Allow-Origin: *
X-Frame-Options: SAMEORIGIN

...
Measured throughput rate is 5.84 Kbytes/sec
HTTP get test passed

The HTTP response code 301, redirecting the URL to https://www.example.com/

Optionally, you can view this and other tests with a packet capture. See Bluecoat packet captures for troubleshooting Edge SWG and Advanced Secure Gateway