Skip to content

Commit bfcde22

Browse files
authored
Merge pull request #55719 from dcbrown16/patch-117
Update application-gateway-faq.md
2 parents 978eba3 + 0a6d9c1 commit bfcde22

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

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

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -408,9 +408,6 @@ But if you'd like to use Application Gateway V2 with only private IP, you can fo
408408
Sample NSG configuration for private IP only access:
409409
![Application Gateway V2 NSG Configuration for private IP access only](./media/application-gateway-faq/appgw-privip-nsg.png)
410410

411-
### Does Application Gateway affinity cookie support SameSite attribute?
412-
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-party context.
413-
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.
414411

415412
## Next steps
416413

0 commit comments

Comments
 (0)