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/application-gateway/configuration-http-settings.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: application-gateway
5
5
author: greg-lindsay
6
6
ms.service: azure-application-gateway
7
7
ms.topic: conceptual
8
-
ms.date: 09/30/2023
8
+
ms.date: 10/03/2024
9
9
ms.author: greglin
10
10
---
11
11
@@ -35,8 +35,7 @@ Please refer to TLS offload and End-to-End TLS documentation for Application Gat
35
35
## Connection draining
36
36
37
37
Connection draining helps you gracefully remove backend pool members during planned service updates. It applies to backend instances that are
38
-
- explicitly removed from the backend pool,
39
-
- removed during scale-in operations, or
38
+
- explicitly removed from the backend pool, or
40
39
- reported as unhealthy by the health probes.
41
40
42
41
You can apply this setting to all backend pool members by enabling Connection Draining in the Backend Setting. It ensures that all deregistering instances in a backend pool don't receive any new requests/connections while maintaining the existing connections until the configured timeout value. This is also true for WebSocket connections.
0 commit comments