mirror of
https://github.com/spring-projects/spring-boot.git
synced 2024-09-03 04:26:12 +08:00
Update docs to reflect change to default Filter dispatcher type
Closes gh-10888 See gh-7467
This commit is contained in:
parent
ec7840e049
commit
b311237906
@ -595,23 +595,8 @@ addition to the underlying component.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
If no `dispatcherType` is specified on a filter registration, it matches
|
||||
`FORWARD`,`INCLUDE`, and `REQUEST`. If async has been enabled, it also matches `ASYNC`.
|
||||
|
||||
If you are migrating a filter that has no `dispatcher` element in `web.xml`, you
|
||||
need to specify a `dispatcherType` yourself, as shown in the following example:
|
||||
|
||||
[source,java,indent=0,subs="verbatim,quotes,attributes"]
|
||||
----
|
||||
@Bean
|
||||
public FilterRegistrationBean myFilterRegistration() {
|
||||
FilterRegistrationBean registration = new FilterRegistrationBean();
|
||||
registration.setDispatcherTypes(DispatcherType.REQUEST);
|
||||
....
|
||||
|
||||
return registration;
|
||||
}
|
||||
----
|
||||
If no `dispatcherType` is specified on a filter registration, `REQUEST` is used. This
|
||||
aligns with the Servlet Specification's default dispatcher type.
|
||||
====
|
||||
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user