Layer7 API Gateway: Using a single port for WebSocket and HTTP(s) traffic
Article ID: 182885
Updated On:
Products
CA API Gateway
API SECURITY
CA API Gateway Enterprise Service Manager (Layer 7)
STARTER PACK-7
CA Microgateway
Issue/Introduction
How can the Gateway be configured to allow WebSocket and HTTP(s) traffic over a single port?
Environment
Release : 9.4
Component : API Gateway
Resolution
The Gateway does not currently allow for WS and HTTP(s) traffic to be served over a single port.
Should you create a listen port, ie 9888 and use this same port to define a WebSocket connection you will receive the below error:
Additionally, if the WS port is created first and then re-used this port for HTTP(s), you will notice it allows you do add it. However, trying to hit any endpoint will result in a 404 error.
Should you create a listen port, ie 9888 and use this same port to define a WebSocket connection you will receive the below error:
Additionally, if the WS port is created first and then re-used this port for HTTP(s), you will notice it allows you do add it. However, trying to hit any endpoint will result in a 404 error.
This is by design and a dedicated port will be required for each.
Feedback
Yes
No
Powered by
