In SGOS 6.5.5.x and later, the behavior of the appliance has changed to handle the HTTP CONNECT request on port 80. Now the
proxy allows CONNECT requests on port 80. Previous to SGOS 6.5.5.x, using any port other than 443 for
CONNECT requests with detect protocol disabled results in the request being denied.
See the following for examples:
CONNECT request behavior on port 80 in SGOS 18.104.22.168:
CONNECT tcp://www.google.de:80/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 user: unauthenticated authentication status='not_attempted' authorization status='not_attempted' EXCEPTION(connect_method_denied): CONNECT to a port other then 443 (the default HTTPS port) are not permitted url.category: Search Engines/Portals@Blue Coat
CONNECT request behavior on port 80 in SGOS 22.214.171.124:
This behavior was updated for WebSocket support in SGOS 126.96.36.199 (to prevent plain WebSocket from failing). In explicit mode, HTTP proxy would receive a HTTP CONNECT on HTTP port (port 80 as a plain WebSocket).
Imported Document ID: 000024393
Subscribing will provide email updates when this Article is updated. Login is required.