title: Confusion in Spring Security Filter Chain
body: <p>I have just started to look into Spring security. I am reading Spring Security reference guide. Here it is written as</p>
  
  <blockquote>
    <p>Using filters="none" operates by creating an empty filter chain in
    Spring Security's FilterChainProxy, whereas the access attributes are
    used to configure the FilterSecurityInterceptor in the single filter
    chain which is created by the namespace configuration. The two are
    applied independently, so if you have an access contraint for a
    sub-pattern of a pattern which has a filters="none" attribute, the
    access constraint will be ignored, even if it is listed first. It
    isn't possible to apply a filters="none" attribute to the pattern /**
    since this is used by the namespace filter chain. In version 3.1
    things are more flexible. You can define multiple filter chains and
    the filters attribute is no longer supported.</p>
  </blockquote>
  
  <p>Can someone elaborate on this note from reference documentation?</p>