Explorar o código

Fix reference to CookieServerCsrfTokenRepository

Issue gh-11959
Steve Riesenberg %!s(int64=2) %!d(string=hai) anos
pai
achega
3d2be56249
Modificáronse 1 ficheiros con 1 adicións e 1 borrados
  1. 1 1
      docs/modules/ROOT/pages/migration/reactive.adoc

+ 1 - 1
docs/modules/ROOT/pages/migration/reactive.adoc

@@ -126,7 +126,7 @@ If configuring CSRF BREACH protection gives you trouble, take a look at these sc
 
 ==== I am using AngularJS or another Javascript framework
 
-If you are using AngularJS and the https://angular.io/api/common/http/HttpClientXsrfModule[HttpClientXsrfModule] (or a similar module in another framework) along with `CookieCsrfTokenRepository.withHttpOnlyFalse()`, you may find that automatic support no longer works.
+If you are using AngularJS and the https://angular.io/api/common/http/HttpClientXsrfModule[HttpClientXsrfModule] (or a similar module in another framework) along with `CookieServerCsrfTokenRepository.withHttpOnlyFalse()`, you may find that automatic support no longer works.
 
 In this case, you can configure Spring Security to validate the raw `CsrfToken` from the cookie while keeping CSRF BREACH protection of the response using a custom `ServerCsrfTokenRequestHandler` with delegation, like so: