You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/api-management/websocket-api.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ API Management supports WebSocket passthrough.
42
42
During the WebSocket passthrough, the client application establishes a WebSocket connection with the API Management gateway, which then establishes a connection with the corresponding backend services. API Management then proxies WebSocket client-server messages.
43
43
44
44
1. The client application sends a WebSocket handshake request to the gateway, invoking the onHandshake operation
45
-
1. The API Management gateway sends WebSocket handshake requests to the corresponding backend service.
45
+
1. The API Management gateway applies configured policies and sends WebSocket handshake requests to the corresponding backend service.
46
46
1. The backend service upgrades a connection to WebSocket.
47
47
1. THe gateway upgrades the corresponding connection to WebSocket.
48
48
1. After the connection pair is established, API Management brokers messages back and forth between the client application and backend service.
@@ -76,7 +76,7 @@ Per the [WebSocket protocol](https://tools.ietf.org/html/rfc6455), when a client
76
76
| Name | Raw name of the WebSocket API. Automatically populates as you type the display name. |
77
77
| WebSocket URL | The base URL with your websocket name. For example: *ws://example.com/your-socket-name*|
78
78
| URL scheme | Accept the default |
79
-
| API URL suffix| Add a URL suffix to identify this specific API in this API Management instance. It has to be unique in this APIM instance. |
79
+
| API URL suffix| Add a URL suffix to identify this specific API in this API Management instance. It has to be unique in this API Management instance. |
80
80
| Products | Associate your WebSocket API with a product to publish it. |
81
81
| Gateways | Associate your WebSocket API with existing gateways. |
82
82
@@ -108,7 +108,7 @@ Use standard API Management and Azure Monitor features to [monitor](api-manageme
108
108
* View API metrics in Azure Monitor
109
109
* Optionally enable diagnostic settings to collect and view API Management gateway logs, which include WebSocket API operations
110
110
111
-
For example, the following screenshot shows recent WebSocket API responses with code `101` from the **ApiManagementGatewayLogs** table. These results indicate the successful switch of the requests from TCP to the WebSocket protocol.
111
+
For example, the following screenshot shows recent WebSocket API responses with code `101` from the **ApiManagementGatewayLogs** table. These results indicate the successful switch of the requests from TCP to the WebSocket protocol.
112
112
113
113
:::image type="content" source="./media/websocket-api/query-gateway-logs.png" alt-text="Query logs for WebSocket API requests":::
0 commit comments