anchor.diff:    routes:
       users:
         path: /myusers/**
  -      sensitiveHeaders: 
  +      sensitiveHeaders:
         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.
  +You can also set sensitive headers, by setting `zuul.sensitiveHeaders`.
  +If `sensitiveHeaders` is set on a route, it overrides the global `sensitiveHeaders` setting.
   
   === Ignored Headers
   
  -In addition to the per-route sensitive headers, you can set a global
  -value for `zuul.ignoredHeaders` for values that should be discarded
  -(both request and response) during interactions with downstream
  -services. By default these are empty, if Spring Security is not on the
  -classpath, and otherwise they are initialized to a set of well-known
  -"security" headers (e.g. involving caching) as specified by Spring
  -Security. The assumption in this case is that the downstream services
  -might add these headers too, and we want the values from the proxy.
  -To not discard these well known security headers in case Spring Security is on the classpath you can set `zuul.ignoreSecurityHeaders` to `false`. This can be useful if you disabled the HTTP Security response headers in Spring Security and want the values provided by downstream services
  +In addition to the route-sensitive headers, you can set a global value called `zuul.ignoredHeaders` for values (both request and response) that should be discarded during interactions with downstream services.
  +By default, if Spring Security is not on the classpath, these are empty.
  +Otherwise, they are initialized to a set of well known "`security`" headers (for example, involving caching) as specified by Spring Security.
  +The assumption in this case is that the downstream services might add these headers, too, but we want the values from the proxy.
  +To not discard these well known security headers when Spring Security is on the classpath, you can set `zuul.ignoreSecurityHeaders` to `false`.
  +Doing so can be useful if you disabled the HTTP Security response headers in Spring Security and want the values provided by downstream services.
   
   === Management Endpoints
   
  -If you are using `@EnableZuulProxy` with the Spring Boot Actuator you
  -will enable (by default) two additional endpoints:
  +By default, if you use `@EnableZuulProxy` with the Spring Boot Actuator, you enable two additional endpoints:
   
   * Routes
   * Filters
   
   ==== Routes Endpoint
   
  -A GET to the routes endpoint at `/routes` will return a list of the mapped
  -routes:
  +A GET to the routes endpoint at `/routes` returns a list of the mapped routes:
   
   .GET /routes
   [source,json]
  
positive.code:       url: https://downstream
  ----
  
  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
  Spring Cloud Netflix 1.1 (in 1.0 the user had no control over headers
  and all cookies flow in both directions).
  
  The `sensitiveHeaders` are a blacklist and the default is not empty,
  so to make Zuul send all headers (except the "ignored" ones) you would
  have to explicitly set it to the empty list. This is necessary if you
  want to pass cookie or authorization headers to your back end. Example:
  
  .application.yml
  [source,yaml]
  
negative.code:       serviceId: users_service
  ----
  
  The preceding example means that HTTP calls to `/myusers` get forwarded to the `users_service` service.
  The route must have a `path` that can be specified as an ant-style pattern, so `/myusers/{asterisk}` only matches one level, but `/myusers/{all}` matches hierarchically.
  
  The location of the backend can be specified as either a `serviceId` (for a service from discovery) or a `url` (for a physical location), as shown in the following example:
  
  .application.yml
  [source,yaml]
  