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-4Lines changed: 2 additions & 4 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: concept-article
8
-
ms.date: 03/19/2025
8
+
ms.date: 04/14/2025
9
9
ms.author: greglin
10
10
---
11
11
@@ -34,9 +34,7 @@ The default affinity cookie name is *ApplicationGatewayAffinity* and you can cha
34
34
35
35
## Connection draining
36
36
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, or
39
-
- reported as unhealthy by the health probes.
37
+
Connection draining helps you gracefully remove backend pool members during planned service updates. It applies to backend instances that are explicitly removed from the backend pool.
40
38
41
39
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 process is also true for WebSocket connections.
0 commit comments