Spring security3 reported an error when configuring the login page not to filter

  java, question

Recently, I was looking at spring security 3. I built an installation document and built a small demo, which is to simulate login interception.
The adopted version is 3.2.5
The following is the xml namespace

<beans xmlns="http://www.springframework.org/schema/beans"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:context="http://www.springframework.org/schema/context"
 xmlns:jdbc="http://www.springframework.org/schema/jdbc" xmlns:jee="http://www.springframework.org/schema/jee"
 xmlns:tx="http://www.springframework.org/schema/tx" xmlns:dubbo="http://code.alibabatech.com/schema/dubbo"
 xmlns:security="http://www.springframework.org/schema/security"
 xsi:schemaLocation="
 http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.2.xsd
 http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.2.xsd
 http://www.springframework.org/schema/jdbc http://www.springframework.org/schema/jdbc/spring-jdbc-3.2.xsd
 http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-3.2.xsd
 http://www.springframework.org/schema/tx  http://www.springframework.org/schema/tx/spring-tx-3.2.xsd
 http://code.alibabatech.com/schema/dubbo
 http://code.alibabatech.com/schema/dubbo/dubbo.xsd
 http://www.springframework.org/schema/security
 http://www.springframework.org/schema/security/spring-security-3.2.xsd">
<!  -identifies that all requests will be blocked and only the role role ROLE_USER can access->
 <security:http auto-config="true">
 <security:intercept-url pattern="/**" access="ROLE_USER"/>
 <!  -identify login.jsp pages that do not need to be filtered. asterisks are used because pages may have parameters above 3.1 when requested. filters are no longer supported, so security-- >
 <security:intercept-url pattern="/login.jsp*" filters="none"/>
 <!  -if blocked, forward directly to the customized login page->
 <security:form-login login-page="/login.jsp"/>
 </security:http>

The previous configuration was based on the document, but the program reported an error, saying that it did not support filters’ recommendation to use security. The same is true for many columns checked online, so the code was modified as follows:

<!  -identifies that all requests will be blocked and only the role role ROLE_USER can access->
 <security:http auto-config="true">
 <security:intercept-url pattern="/**" access="ROLE_USER"/>
 <!  -identify login.jsp pages that do not need to be filtered. asterisks are used because pages may have parameters above 3.1 when requested. filters are no longer supported, so security-- >
 <security:intercept-url pattern="/login.jsp*" security="none"/>
 <!  -if blocked, forward directly to the customized login page->
 <security:form-login login-page="/login.jsp"/>
 </security:http>

As a result, the program still reported an error saying:
‘security’ is not allowed to appear in element ‘security:intercept-url’.
How do you know?

Dear heroes, is there nothing you know, or is my question not detailed enough?