Inspectopedia 2026.3 Help

Request matcher configured after 'anyRequest()'

Reports request-matcher registrations (requestMatchers, mvcMatchers, antMatchers, regexMatchers) that are chained after anyRequest() inside an authorizeHttpRequests/authorizeRequests block.

anyRequest() must be the last matcher in the authorization chain. Configuring another matcher after it makes Spring Security fail at startup with Can't configure requestMatchers after anyRequest.

Incorrect:

http.authorizeHttpRequests(auth -> auth .requestMatchers("/", "/home").permitAll() .anyRequest().authenticated() .requestMatchers("/admin/**").hasRole("ADMIN") // reports: configured after anyRequest() );

Correct (move anyRequest() to the end):

http.authorizeHttpRequests(auth -> auth .requestMatchers("/", "/home").permitAll() .requestMatchers("/admin/**").hasRole("ADMIN") .anyRequest().authenticated() );

Locating this inspection

By ID

Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.

SpringSecurityMatchersAfterAnyRequest
Via Settings dialog

Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.

Settings or Preferences | Editor | Inspections | Spring | Spring Security

Inspection ID: SpringSecurityMatchersAfterAnyRequest

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection SpringSecurityMatchersAfterAnyRequest

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

Inspection Details

By default bundled with:

IntelliJ IDEA 2026.3, Qodana for JVM 2026.3,

Last modified: 20 November 2026