Add a Websocket-based application
HTTP and WebSocket both are communication protocols used in client-server communication. HTTP is unidirectional where the client sends the request and a server responds. WebSockets, on the other hand, is a bidirectional and a full-duplex protocol used between the client and server.
Access Gateway supports WebSocket-based applications by adding a policy directive to those URIs associated with WebSocket end points. The following sections describe the tasks required to define a header-based application and then create a policy for each web socket-based URI.
Ensure you have available:
- An appropriate DNS entry for both the WebSocket application and the external exposed new URL exist.
Value Description https://external.domain.com External application. The URL clients use https://internal.domain.com Protected application URL.
- A list of any required application header attributes exists along with their expected content.
- A list of all WebSocket-based URIs that exist, so you can tag each as using WebSocket policy directives.
The Access Gateway administrator usually performs all tasks in this workflow.
|Create a containing group|
|Create header application|
|Add additional attributes|
|Add required access policy|
|Test the application|