Skip to content

Commit 3055a79

Browse files
authored
Merge pull request #105110 from surajmb/patch-17
Update FAQ for SameSite
2 parents c8dfc7b + f40e5c0 commit 3055a79

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

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

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

408+
### Does Application Gateway affinity cookie support SameSite attribute?
409+
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 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.
408411

409412
## Next steps
410413

0 commit comments

Comments
 (0)