Skip to content

Commit f40e5c0

Browse files
surajmbvhorne
andauthored
Update articles/application-gateway/application-gateway-faq.md
Co-Authored-By: Vic <[email protected]>
1 parent 8dccd97 commit f40e5c0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/application-gateway-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -407,7 +407,7 @@ Sample NSG configuration for private IP only access:
407407

408408
### Does Application Gateway affinity cookie support SameSite attribute?
409409
Yes, the [Chromium browser](https://www.chromium.org/Home) [v80 update](https://chromiumdash.appspot.com/schedule) introduced a mandate on HTTP cookies without SameSite attribute to be treated as SameSite=Lax. This means that the Application Gateway affinity cookie won't be sent by the browser in a third-pary context.
410-
To support this scenario, Application Gateway will be injecting another cookie called ApplicationGatewayAffinityCORS in addition to the existing ApplicationGatewayAffinity cookie, which is similar, but this cookie will now have two more attributes SameSite=None; Secure” added to it so that sticky session can be maintained even for cross-origin requests. See [cookie based affinity section](configuration-overview.md#cookie-based-affinity) for more information.
410+
To support this scenario, Application Gateway injects another cookie called *ApplicationGatewayAffinityCORS* in addition to the existing *ApplicationGatewayAffinity* cookie. These cookies are similar, but the *ApplicationGatewayAffinityCORS* cookie has two more attributes added to it: *SameSite=None; Secure*. These attributes maintain sticky sessions even for cross-origin requests. See the [cookie based affinity section](configuration-overview.md#cookie-based-affinity) for more information.
411411

412412
## Next steps
413413

0 commit comments

Comments
 (0)