|
@@ -323,7 +323,7 @@ For details, refer to the <<servlet-csrf-configure-custom-repository>> section.
|
|
|
|
|
|
If a token does expire, you might want to customize how it is handled by specifying a custom `AccessDeniedHandler`.
|
|
If a token does expire, you might want to customize how it is handled by specifying a custom `AccessDeniedHandler`.
|
|
The custom `AccessDeniedHandler` can process the `InvalidCsrfTokenException` any way you like.
|
|
The custom `AccessDeniedHandler` can process the `InvalidCsrfTokenException` any way you like.
|
|
-For an example of how to customize the `AccessDeniedHandler` refer to the provided links for both <<nsa-access-denied-handler,xml>> and https://github.com/spring-projects/spring-security/blob/3.2.0.RC1/config/src/test/groovy/org/springframework/security/config/annotation/web/configurers/NamespaceHttpAccessDeniedHandlerTests.groovy#L64[Java configuration].
|
|
|
|
|
|
+For an example of how to customize the `AccessDeniedHandler` refer to the provided links for both <<nsa-access-denied-handler,xml>> and https://github.com/spring-projects/spring-security/blob/3.2.0.RC1/config/src/test/java/org/springframework/security/config/annotation/web/configurers/NamespaceHttpAccessDeniedHandlerTests.java#L64[Java configuration].
|
|
// FIXME: We should add a custom AccessDeniedHandler section in the reference and update the links above
|
|
// FIXME: We should add a custom AccessDeniedHandler section in the reference and update the links above
|
|
|
|
|
|
|
|
|