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
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ During the WebSocket passthrough, the client application establishes a WebSocket
53
53
1. When either side disconnects, API Management terminates the corresponding connection.
54
54
55
55
> [!NOTE]
56
-
> The client-side and backend-side connections consist of one-to-one mapping.
56
+
> Client-to-backend connections consist of one-to-one mappings. The same WebSocket session cannot be distributed across multiple backends.
57
57
58
58
## onHandshake operation
59
59
@@ -120,6 +120,7 @@ The following are the current restrictions of WebSocket support in API Managemen
120
120
* WebSocket APIs support the following valid buffer types for messages: Close, BinaryFragment, BinaryMessage, UTF8Fragment, and UTF8Message.
121
121
* Currently, the [set-header](set-header-policy.md) policy doesn't support changing certain well-known headers, including `Host` headers, in onHandshake requests.
122
122
* During the TLS handshake with a WebSocket backend, API Management validates that the server certificate is trusted and that its subject name matches the hostname. With HTTP APIs, API Management validates that the certificate is trusted but doesn’t validate that hostname and subject match.
123
+
* WebSocket connections cannot be distributed or load-balanced across multiple backends because, once established, each connection is maintained one-to-one between the client and backend.
123
124
124
125
For WebSocket connection limits, see [API Management limits](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-api-management-limits).
Copy file name to clipboardExpand all lines: articles/azure-functions/dotnet-isolated-in-process-differences.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Use the following table to compare feature and functional differences between th
30
30
|[Supported .NET versions](#supported-versions)| Long Term Support (LTS) versions,<br/>Standard Term Support (STS) versions,<br/>.NET Framework | Long Term Support (LTS) versions, ending with .NET 8 |
| Output binding interactions | Return values in an expanded model with:<br/> - single or [multiple outputs](dotnet-isolated-process-guide.md#multiple-output-bindings)<br/> - arrays of outputs| Return values (single output only),<br/>`out` parameters,<br/>`IAsyncCollector`|
0 commit comments