From 46475a566fcd630857dc7cdc6f0e1101db10bbf3 Mon Sep 17 00:00:00 2001 From: Some developer Date: Tue, 29 Aug 2023 11:29:44 -0500 Subject: [PATCH] Fix grammar --- docs/modules/ROOT/pages/servlet/authentication/logout.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/servlet/authentication/logout.adoc b/docs/modules/ROOT/pages/servlet/authentication/logout.adoc index 6b2ac5697dc..88dfab33203 100644 --- a/docs/modules/ROOT/pages/servlet/authentication/logout.adoc +++ b/docs/modules/ROOT/pages/servlet/authentication/logout.adoc @@ -80,7 +80,7 @@ Xml:: and no authorization changes are necessary since it simply adjusts the `LogoutFilter`. [[permit-logout-endpoints]] -However, if you stand up your own logout success endpoint (or in a rare case, <>), say using {spring-framework-reference-url}web.html#spring-web[Spring MVC], you will need permit it in Spring Security. +However, if you stand up your own logout success endpoint (or in a rare case, <>), say using {spring-framework-reference-url}web.html#spring-web[Spring MVC], you will need to permit it in Spring Security. This is because Spring MVC processes your request after Spring Security does. You can do this using `authorizeHttpRequests` or `` like so: