Solutions

WebSocket console error, can't connect to Deployment Automation using proxy HTTP protocol
Back to all Solutions Back Rate Content Rate this Page



ID:    S141934
Published:    02 November 2016
Updated:    15 December 2016

Operating System(s)

  • All Unix
  • All Windows

Product(s)

  • Deployment Automation 6.1.3
 

Description

When HTML5 WebSockets are used, the communication protocol between the client and server upgrades from the HTTP to WebSockets during an initial handshake. The WebSocket protocol simply establishes the WebSocket handshake and the format for the WebSocket data frames. It does nothing different if there is a proxy server. 

 

The data being passed between the Deployment Automation Web browser user interface (client) and server using WebSockets are the counters shown in the upper right of the user interface that show number of processes and number of approvals. You cannot turn off the WebSocket communication in Deployment Automation, so you must configure your proxy server as needed to support WebSocket protocol.

 

The following sections describe what will happen in various scenarios where WebSocket protocol is used with proxy servers. 

Resolution

Use these to determine if you may need to configure your proxy server to resolve any WebSocket issues when connecting to Deployment Automation through a proxy server. 
 
Explicit Proxy Servers with Unencrypted WebSocket Connections
 
In this scenario, the connection will probably work. When an explicit proxy server allows the HTTP CONNECT method, the WebSocket connection and data flow should be allowed through the proxy server.
 
Transparent Proxy Servers with Unencrypted WebSocket Connections
 
In this scenario, the connection will probably fail. The browser does not issue the HTTP CONNECT method and when the proxy server forwards a request through the WebSocket to the server, it is expected to strip off the connection header. Because it doesn't know to do that, the handshake will typically fail immediately. 

Explicit Proxy Servers with Encrypted WebSocket Connections
 
In this scenario, the connection will probably work. When an explicit proxy server allows the HTTP CONNECT method, the WebSocket connection and encrypted data flow should be allowed through the proxy server. 
 
Transparent Proxy Servers with Encrypted WebSocket Connections
 
In this scenario, the connection may work, depending on whether WebSockets Secure with TLS is used (//wss: rather than //ws:). When a transparent proxy server is used, the Web browser does not know about the proxy server, so no HTTP CONNECT method is sent, and the proxy may allow the encrypted data through. 

Applies To

Release Automation 6.1.3

Rate this Solution

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs