Skip to content

Commit fff74ab

Browse files
committed
react to feedback
1 parent 33d328c commit fff74ab

File tree

1 file changed

+2
-2
lines changed
  • aspnetcore/security/data-protection/configuration

1 file changed

+2
-2
lines changed

aspnetcore/security/data-protection/configuration/scaling.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ uid: security/data-protection/configuration/scaling
1616
ASP.NET Core [Data Protection](xref:security/data-protection/introduction) is a library that provides a cryptographic API to protect data. Data Protection protects anti-forgery tokens, authentication cookies, and other sensitive data. However, in some distributed environments that don't put data protection keys in shared storage, when an app scales horizontally by adding more instances:
1717

1818
* It's necessary to explicitly configure Data Protection to establish a shared storage location for Data Protection keys.
19-
* There’s ***NO*** guarantee that the HTTP POST request, used to submit a form, will be routed to the same instance that served the initial page via an HTTP GET request. If the requests are handled by different instances, the anti-forgery tokens aren’t synchronized, and an exception occurs. Sticky sessions via [ARR Affinity](/azure/app-service/manage-automatic-scaling?#how-does-arr-affinity-affect-automatic-scaling) routes user requests to the same node, however, ARR can reduce the scalability of a web farm.
19+
* There’s ***NO*** guarantee that the HTTP POST request, used to submit a form, will be routed to the same instance that served the initial page via an HTTP GET request. If the requests are handled by different instances, the anti-forgery tokens aren’t synchronized, and an exception occurs. Sticky sessions via [ARR Affinity](/azure/app-service/manage-automatic-scaling?#how-does-arr-affinity-affect-automatic-scaling) routes user requests to the same node. However, ARR can reduce the scalability of a web farm.
2020

2121
The following distributed environments provide automatic key storage in a shared location:
2222

@@ -29,7 +29,7 @@ The following scenarios do ***NOT*** provide automatic key storage in a shared l
2929
* Separate [deployment slots](/azure/app-service/deploy-staging-slots), such as Staging and Production.
3030
* Azure Container Apps built using ASP.NET Core Kestrel 7.0 or earlier. For more information see [Autoscaling considerations
3131
](/azure/container-apps/dotnet-overview#autoscaling-considerations).
32-
* Asp.net core apps hosted on multiple non-Azure VMs that don't use server affinity. Server affinity doesn't provide a shared location, it makes shared storage unnecessary. Server affinity ensures that a client's requests are always routed to the same server. For more information see [Server affinity](/azure/app-service/manage-automatic-scaling?#how-does-arr-affinity-affect-automatic-scaling).
32+
* Asp.net core apps hosted on multiple non-Azure VMs that don't use server affinity. Server affinity ensures that a client's requests are always routed to the same server so having the keys in a shared location is not necessary. For more information see [Server affinity](/azure/app-service/manage-automatic-scaling?#how-does-arr-affinity-affect-automatic-scaling).
3333

3434
:::moniker-end
3535

0 commit comments

Comments
 (0)