【spring security3.1 不再支持 filters="none" 解决办法】
最近关于spring security3.1 不再支持 filters="none" 我们有了新的解决办法,方法如下:
[java]
<security:http auto-config="true">
<!-- login-page -->
<security:form-login login-page="/login.jsp"/>
<!-- 对登录页面不进行拦截, 后面的*主要是请求页面可能会带有一些参数-->
<security:intercept-url pattern="/login.jsp*" filters="none"/>
<security:intercept-url pattern="/**" access ="ROLE_USER"/>
</security:http>
<security:http auto-config="true">
<!-- login-page -->
<security:form-login login-page="/login.jsp"/>
<!-- 对登录页面不进行拦截, 后面的*主要是请求页面可能会带有一些参数-->
<security:intercept-url pattern="/login.jsp*" filters="none"/>
<security:intercept-url pattern="/**" access ="ROLE_USER"/>
</security:http>
[html]
<security:http auto-config="true">
<!-- login-page -->
<security:form-login login-page="/login.jsp"/>
<!-- 对登录页面不进行拦截, 后面的*主要是请求页面可能会带有一些参数-->
<security:intercept-url pattern="/login.jsp*" filters="none"/>
<security:intercept-url pattern="/**" access ="ROLE_USER"/>
</security:http>
<security:http auto-config="true">
<!-- login-page -->
<security:form-login login-page="/login.jsp"/>
<!-- 对登录页面不进行拦截, 后面的*主要是请求页面可能会带有一些参数-->
<security:intercept-url pattern="/login.jsp*" filters="none"/>
<security:intercept-url pattern="/**" access ="ROLE_USER"/>
</security:http>
系统报错如下:
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: The use of "filters='none'" is no longer supported. Please define a separate <http> element for the pattern you want to exclude and use the attribute "security='none'".
Offending resource: class path resource [applicationContext.xml]