Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update Spring Security filter dispatcher types docs to reflect change in default value #33252

Closed
wants to merge 1 commit into from
Closed

Update Spring Security filter dispatcher types docs to reflect change in default value #33252

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions ...t-autoconfigure/src/main/resources/META-INF/additional-spring-configuration-metadata.json
View file
Open in desktop
Expand Up @@ -2722,6 +2722,8 @@
"defaultValue": [
"async",
"error",
"forward",
"include",
"request"
]
},
Expand Down
3 changes: 0 additions & 3 deletions spring-boot-project/spring-boot-docs/src/docs/asciidoc/web/servlet.adoc
View file
Open in desktop
Expand Up @@ -397,9 +397,6 @@ The error page filter can only forward the request to the correct error page if
By default, WebSphere Application Server 8.0 and later commits the response upon successful completion of a servlet's service method.
You should disable this behavior by setting `com.ibm.ws.webcontainer.invokeFlushAfterService` to `false`.

If you are using Spring Security and want to access the principal in an error page, you must configure Spring Security's filter to be invoked on error dispatches.
To do so, set the `spring.security.filter.dispatcher-types` property to `async, error, forward, request`.



[[web.servlet.spring-mvc.cors]]
Expand Down