When using Shiro and MVC integration, the login verification is Shiro with the Formauthenticationfilter filter, the result configuration Successurl can not be configured as a *.do format, can only be configured as "/" or not set, the default is also "/"。 and in Web. XML, the path to MVC can only be configured as "/". This is the only way to use it properly. This, in turn, can cause MVC to intercept static resources. Although the network said there are many MVC configuration methods to filter static resources, but I do not know for a moment what is the reason, with the <mvc:resource/> method, as long as the addition, the controller load will be invalidated.
For the time being yet to try out what is the reason, think of it as if you can only implement the filter. If a great God has met and has solved this problem, please enlighten me.
The conflict between the Shiro framework and the SPRINGMVC