anchor.diff:          unit: seconds
   ----
   
  -Conditional filtering depending on the anonymous or logged in user. Cause the *bucket4j.filters[0].strategy* is *first*
  -you havn't to check in the second rate-limit if the user is logged in cause the first rate-limit check if the user is unauthenticated.
  -If its the case no other rate-limit will be evaluated.
  +Conditional filtering depending on the anonymous or logged in user. Because the *bucket4j.filters[0].strategy* is *first*
  +you havn't to check in the second rate-limit that the user is logged in. Only the first one is executed.
   
   [source,yml]
   ----
  
positive.code: 
  ==== first
  
  The *first* is the default strategy. This the default strategy which only execute one rate limit.
  So if you check in the first rate limit if the user is authenticated and the user is not you know that the other rate-limits handles
  authenticated users.
  
  ==== all
  
  
negative.code: 
  ==== Expression
  
  The expression based filter type provides the most flexible one and uses the Spring Expression Language (SpEL). https://docs.spring.io/spring/docs/current/spring-framework-reference/html/expressions.html#expressions-spel-compilation[The expression compiles to a Java class which will be used].
  It provides an easy way to configure the throttling in different environments without writing one line of code.
  
  *Limiting based on IP-Address*:
  [source]
  