From 2b4a1af88ff3e268224b697ffc68b8872e183b12 Mon Sep 17 00:00:00 2001 From: guardrex <1622880+guardrex@users.noreply.github.com> Date: Wed, 25 Sep 2024 11:30:47 -0400 Subject: [PATCH] Updates --- aspnetcore/security/anti-request-forgery.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/security/anti-request-forgery.md b/aspnetcore/security/anti-request-forgery.md index 73db06c4f3..db7a8fbe3b 100644 --- a/aspnetcore/security/anti-request-forgery.md +++ b/aspnetcore/security/anti-request-forgery.md @@ -127,7 +127,7 @@ Automatic generation of antiforgery tokens for HTML form elements can be disable > [!NOTE] > [Razor Pages](xref:razor-pages/index) are automatically protected from XSRF/CSRF. For more information, see [XSRF/CSRF and Razor Pages](xref:razor-pages/index#xsrfcsrf-and-razor-pages-1). -The most common approach to ing against CSRF attacks is to use the *Synchronizer Token Pattern* (STP). STP is used when the user requests a page with form data: +The most common approach to protecting against CSRF attacks is to use the *Synchronizer Token Pattern* (STP). STP is used when the user requests a page with form data: 1. The server sends a token associated with the current user's identity to the client. 1. The client sends back the token to the server for verification.