anchor.diff:        stripPrefix: false
   ----
   
  -In this example requests to "/myusers/101" will be forwarded to "/myusers/101" on the "users" service.
  +In this example, requests to "/myusers/101" will be forwarded to "/myusers/101" on the "users" service.
   
   The `zuul.routes` entries actually bind to an object of type `ZuulProperties`. If you
   look at the properties of that object you will see that it also has a "retryable" flag.
  
positive.code: picks up a header "X-Forwarded-Prefix" ("/myusers" in the examples
  above).
  
  An application with the `@EnableZuulProxy` could act as a standalone
  server if you set a default route ("/"), for example `zuul.route.home:
  /` would route all traffic (i.e. "/{all}") to the "home" service.
  
  If more fine-grained ignoring is needed, you can specify specific patterns to ignore.
  These patterns are being evaluated at the start of the route location process, which
  means prefixes should be included in the pattern to warrant a match. Ignored patterns
  span all services and supersede any other route specification.
  
  
negative.code:     users:
        path: /myusers/**
        sensitiveHeaders: Cookie,Set-Cookie,Authorization
        url: https://downstream
  ----
  
  Sensitive headers can also be set globally by setting `zuul.sensitiveHeaders`. If `sensitiveHeaders` is set on a route, this will override the global `sensitiveHeaders` setting.
  
  NOTE: this is the default value for `sensitiveHeaders`, so you don't
  need to set it unless you want it to be different. N.B. this is new in
  