anchor.diff:  
   
   [[release-numbering]]
  -==== Release Numbering
  +=== Release Numbering
   It is useful to understand how Spring Security release numbers work, as it will help you identify the effort (or lack thereof) involved in migrating to future releases of the project. Each release uses a standard triplet of integers: MAJOR.MINOR.PATCH. The intent is that MAJOR versions are incompatible, large-scale upgrades of the API. MINOR versions should largely retain source and binary compatibility with older minor versions, thought there may be some design changes and incompatible udates. PATCH level should be perfectly compatible, forwards and backwards, with the possible exception of changes which are to fix bugs and defects.
   
   The extent to which you are affected by changes will depend on how tightly integrated your code is. If you are doing a lot of customization you are more likely to be affected than if you are using a simple namespace configuration.
  
positive.code: | Required if you are using JSR-250 method-security annotations (optional).
  |===
  
  ==== spring-security-remoting
  This module is typically required in web applications which use the Servlet API.
  
  .Remoting Dependencies
  
negative.code: When we looked at how to set up web security using <<ns-web-xml,namespace configuration>>, we used a `DelegatingFilterProxy` with the name "springSecurityFilterChain". You should now be able to see that this is the name of the `FilterChainProxy` which is created by the namespace.
  
  
  ==== Bypassing the Filter Chain
  You can use the attribute `filters = "none"` as an alternative to supplying a filter bean list. This will omit the request pattern from the security filter chain entirely. Note that anything matching this path will then have no authentication or authorization services applied and will be freely accessible. If you want to make use of the contents of the `SecurityContext` contents during a request, then it must have passed through the security filter chain. Otherwise the `SecurityContextHolder` will not have been populated and the contents will be null.
  
  
  === Filter Ordering
  The order that filters are defined in the chain is very important. Irrespective of which filters you are actually using, the order should be as follows:
  
  * `ChannelProcessingFilter`, because it might need to redirect to a different protocol
  