From ac0668ac4ad877b28465a42eaa8a5156bc8f4cff Mon Sep 17 00:00:00 2001 From: maliming Date: Mon, 6 Oct 2025 11:14:25 +0800 Subject: [PATCH] Clarify ABP CSRF/Antiforgery compatibility in docs --- docs/en/framework/infrastructure/csrf-anti-forgery.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/framework/infrastructure/csrf-anti-forgery.md b/docs/en/framework/infrastructure/csrf-anti-forgery.md index df36c4f985..f35e218774 100644 --- a/docs/en/framework/infrastructure/csrf-anti-forgery.md +++ b/docs/en/framework/infrastructure/csrf-anti-forgery.md @@ -17,7 +17,7 @@ Once you enable it; Especially, the second point is a pain for your clients and unnecessarily consumes your server resources. -> You can read more about the ASP.NET Core antiforgery system in its own [documentation](https://docs.microsoft.com/en-us/aspnet/core/security/anti-request-forgery). +> You can use any ASP.NET Core antiforgery features, like `ValidateAntiForgeryToken`, `AutoValidateAntiforgeryToken`, or `IgnoreAntiforgeryToken`, for more information, see the [official documentation](https://docs.microsoft.com/en-us/aspnet/core/security/anti-request-forgery). ## The Solution