When using Spring MVC, unlike other endpoints, controller and REST controller endpoints use Ant path matching

When we create WebMvcEndpointHandlerMapping we use the path pattern parser from the MVC auto-configuration:

https://github.com/spring-projects/spring-boot/blob/17bdc526f6af27478f45a828017e28c402c04e95/spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/endpoint/web/servlet/WebMvcEndpointManagementContextConfiguration.java#L86-L88

However, when we create ControllerEndpointHandlerMapping, we don’t pass in a path pattern parser:

https://github.com/spring-projects/spring-boot/blob/17bdc526f6af27478f45a828017e28c402c04e95/spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/endpoint/web/servlet/WebMvcEndpointManagementContextConfiguration.java#L116-L117

As a result, the default Ant-based path matching will be used. This feels inconsistent. However, there’s a risk that changing it will break users controller and rest controller endpoints if they have implementations that rely on some capabilities of the Ant-based matching that the path pattern parser doesn’t support. We may decide that we can’t do anything about this until 3.0.

[wilkinsona]

It’s #31700.

[wilkinsona]

That doesn’t appear to be related to this issue which is specifically about request matching, not handler mapping beans. Please follow up on Stack Overflow or Gitter, but I think you’ll have to try to change PSTraceFilterAutoConfiguration. You cannot assume that there will only be a single RequestMappingHandlerMapping bean in the context. Spring MVC supports any number of them.