From ce995a01789e70516ec128ae7092bb8438b8bb89 Mon Sep 17 00:00:00 2001 From: Angel Gruevski <81828120+angel-gruevski@users.noreply.github.com> Date: Sat, 6 Apr 2024 15:53:08 +0200 Subject: [PATCH] Correct a mistake in the documentation related to RequestCacheAwareFilter Corrected a mistake in the documentation for the Spring Architecture where it was mentioned that RequestCacheAwareFilter is used to save the HttpServletRequest instead of the ExceptionTranslationFilter Closes gh-14855 --- docs/modules/ROOT/pages/servlet/architecture.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/modules/ROOT/pages/servlet/architecture.adoc b/docs/modules/ROOT/pages/servlet/architecture.adoc index 0ed5a73402b..fed9035787a 100644 --- a/docs/modules/ROOT/pages/servlet/architecture.adoc +++ b/docs/modules/ROOT/pages/servlet/architecture.adoc @@ -442,7 +442,7 @@ In Spring Security this is done by saving the `HttpServletRequest` using a <> is what uses the `RequestCache` to save the `HttpServletRequest`. +The <> uses the `RequestCache` to get the saved `HttpServletRequest` after the user authenticates, while the `ExceptionTranslationFilter` uses the `RequestCache` to save the `HttpServletRequest` after it detects `AuthenticationException`, before redirecting the user to the login endpoint. By default, an `HttpSessionRequestCache` is used. The code below demonstrates how to customize the `RequestCache` implementation that is used to check the `HttpSession` for a saved request if the parameter named `continue` is present. @@ -510,7 +510,7 @@ XML:: [[requestcacheawarefilter]] === RequestCacheAwareFilter -The {security-api-url}org/springframework/security/web/savedrequest/RequestCacheAwareFilter.html[`RequestCacheAwareFilter`] uses the <> to save the `HttpServletRequest`. +The {security-api-url}org/springframework/security/web/savedrequest/RequestCacheAwareFilter.html[`RequestCacheAwareFilter`] uses the <> to replay the original request. [[servlet-logging]] == Logging