From 810c299b9d84760b564b2b1bd9d4e7b866efbc3b Mon Sep 17 00:00:00 2001
From: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
Date: Tue, 7 Jan 2025 15:37:00 -1000
Subject: [PATCH] Update anti-request-forgery.md

---
 aspnetcore/security/anti-request-forgery.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/aspnetcore/security/anti-request-forgery.md b/aspnetcore/security/anti-request-forgery.md
index 4e1a3481d0..227753213d 100644
--- a/aspnetcore/security/anti-request-forgery.md
+++ b/aspnetcore/security/anti-request-forgery.md
@@ -159,9 +159,9 @@ Calling <xref:Microsoft.Extensions.DependencyInjection.MvcServiceCollectionExten
 
 ## Multiple browser tabs and the Synchronizer Token Pattern
 
-With the Synchronizer Token Pattern, only the most recently loaded page is guaranteed to contain a valid antiforgery token. Apps that wish to support multiple tabs should test supported browsers and log failures. ***Using multiple tabs can be problematic***. For example, if a user opens multiple tabs, requests made from previously loaded tabs might fail with an error: `Antiforgery token validation failed. The antiforgery cookie token and request token do not match`
- 
- Consider alternative CSRF protection patterns if this poses an issue.
+Multiple tabs logged in as different users, or one logged in as anonymous, are not supported.
+
+With the Synchronizer Token Pattern, only the most recently posted page is guaranteed to contain a valid antiforgery token. Apps that wish to support multiple tabs should test supported browsers and log failures.
 
 ## Configure antiforgery with `AntiforgeryOptions`