BUG: Dual Behavior of Tests into Spring Boot MockMvc and Curl

[ejpg-sys]

The Spring Test Context Framework has a behavior analysis problem when given to test cases.

Ie.: With a Jakarta Servlet Filter implementation in Combination with Spring Boot Registration, into doFilter after a if/else, the chain should follow or be redirected. With this implementation and execution, with curl command line is possible check the behavior of authorization (ok/unathorized). But, if the same are executed with MockMvc, the filter is ignored and the Spring do more things against the initial resource lookup. So, in the first time, with curl the response are ok/unauthorized, but with MockMvc are ok/ok/bad_request/ok.

Regards!

[bclozel]

Thanks for getting in touch, but it feels like this is a question that would be better suited to Stack Overflow. As mentioned in the guidelines for contributing, we prefer to use the issue tracker only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add some more details if you feel this is a genuine bug.

[ejpg-sys]

It's a bug because the behavior of the framework should be the same as well spected in another hand.

[bclozel]

@ejpg-sys please provide a minimal sample application created using start.spring.io showing the problem and we'll reconsider the issue.

[ejpg-sys]

@bclozel follow-up the sample application as described on this issue: https://github.com/ejpg-sys/issue-spring-mockmvc