You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Storing the request matcher outside of the for loop means that
if one of the SecurityFilterChain instances is not of type
DefaultSecurityFilterChain, then the error may print out an
earlier request matcher instead of the current one.
Instead, this commit changes to print out the entire filter chain
so that it can be inside of the for loop, regardless of type.
Issue gh-15220
"A filter chain that matches any request has already been configured, which means that this filter chain for ["
306
-
+ matcher
304
+
"A filter chain that matches any request has already been configured, which means that this filter chain ["
305
+
+ securityFilterChain
307
306
+ "] will never get invoked. Please use `HttpSecurity#securityMatcher` to ensure that there is only one filter chain configured for 'any request' and that the 'any request' filter chain is published last.");
308
307
if (securityFilterChaininstanceofDefaultSecurityFilterChaindefaultSecurityFilterChain) {
0 commit comments