How to solve the excludePathPatterns ignore failure of springboot Interceptor interceptor

Today, I would like to share with you the relevant knowledge points about how to solve the failure of springboot Interceptor interceptor excludePathPatterns. The content is detailed and the logic is clear. I believe most people still know too much about this knowledge, so share this article for your reference. I hope you can get something after reading this article. Let's take a look.

Springboot Interceptor interceptor excludePathPatterns ignore failure

The excludePathPatterns method excludes access paths, but when the url path you exclude does not exist in the project, springboot will program / error the path, so it cannot be excluded.

For example, the following code:

Registry.addInterceptor (new MyInterceptor ()) .addPathPatterns ("/ *") .excludePathPatterns ("/ login")

If the / login access path does not exist in the project, then when you access http://xxxx/login, it will still be blocked because it becomes the error path, which can also be verified by request.getRequestUrl in your custom interceptor.

But if you are using a normal springmvc project, it will not be blocked, but because there is no login path, the 404 page will be displayed.

Invalid springboot interceptor exclusion, invalid excludePathPatterns in springboot

You can access the breakpoint to see if the access path and the configured path are the same or invalid.

These are all the contents of the article "how to solve the failure of springboot Interceptor interceptor excludePathPatterns neglect". Thank you for reading! I believe you will gain a lot after reading this article. The editor will update different knowledge for you every day. If you want to learn more knowledge, please pay attention to the industry information channel.