anchor.diff:  
   [[nsa-filter-chain-filters]]
   * **filters**
  -A comma separated list of references to Spring beans that implement `Filter`. The value "none" means that no `Filter`'s should be used for this `FilterChain`.
  +A comma separated list of references to Spring beans that implement `Filter`. The value "none" means that no `Filter` should be used for this `FilterChain`.
   
   
   [[nsa-filter-chain-pattern]]
  
positive.code: * **ref**
  Defines a reference to a Spring bean that implements `AuthenticationProvider `.
  
  If you have written your own `AuthenticationProvider` implementation (or want to configure one of Spring Security's own implementations as a traditional bean for some reason, then you can use the following syntax to add it to the internal `ProviderManager`'s list:
  
  [source,xml]
  ----
  
negative.code: </filter-mapping>
  ----
  
  Notice that the filter is actually a `DelegatingFilterProxy`, and not the class that will actually implement the logic of the filter. What `DelegatingFilterProxy` does is delegate the `Filter` methods through to a bean which is obtained from the Spring application context. This enables the bean to benefit from the Spring web application context lifecycle support and configuration flexibility. The bean must implement `javax.servlet.Filter` and it must have the same name as that in the `filter-name` element. Read the Javadoc for `DelegatingFilterProxy` for more information
  
  
  [[filter-chain-proxy]]
  