Skip to content

Commit 135dc45

Browse files
authored
Merge pull request #92609 from Rick-Anderson/patch-2
Update how-to-troubleshoot-application-gateway-session-affinity-issue…
2 parents 5bd27f8 + c106475 commit 135dc45

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Learn how to diagnose and resolve session affinity issues with Azure Application
1919

2020
## Overview
2121

22-
The cookie-based session affinity feature is useful when you want to keep a user session on the same server. By using gateway-managed cookies, the Application Gateway can direct subsequent traffic from a user session to the same server for processing. This is important in cases where session state is saved locally on the server for a user session.
22+
The cookie-based session affinity feature is useful to keep a user session on the same server. By using gateway-managed cookies, the Application Gateway can direct subsequent traffic from a user session to the same server for processing. This is important in cases where session state is saved locally on the server for a user session. Session affinity is also known as sticky sessions.
2323

2424
> [!NOTE]
2525
> Application Gateway v1 issues a cookie called ARRAffinity, which is used to direct traffic to the same backend pool member. In Application Gateway v2, this cookie has been renamed to ApplicationGatewayAffinity. For the purposes of this document, ApplicationGatewayAffinity will be used as an example, ARRAffinity can be substituted in where applicable for Application Gateway v1 instances.

0 commit comments

Comments
 (0)