anchor.diff:  those paths are added. If multiple routes with the same path are
   used, the oldest takes priority.
   
  -A consequence of this behavior is that if you have two routes for a hostname: an
  -older one and a newer one. If someone else has a route for the same hostname
  +A consequence of this behavior is that if you have two routes for a host name: an
  +older one and a newer one. If someone else has a route for the same host name
   that they created between when you created the other two routes, then if you
  -delete your older route, your claim to the hostname will no longer be in effect.
  -The other namespace now claims the hostname and your claim is lost.
  +delete your older route, your claim to the host name will no longer be in effect.
  +The other namespace now claims the host name and your claim is lost.
   
   .A Route with a Specified Host:
   ====
  
positive.code: link:https://en.wikipedia.org/wiki/Server_Name_Indication[SNI] for serving
  custom certificates. Any non-SNI traffic received on port 443 is handled with
  TLS termination and a default certificate (which may not match the requested
  hostname, resulting in validation errors).
  ====
  
  Secured routes can use any of the following three types of secure TLS
  
negative.code: == Path Based Routes
  Path based routes specify a path component that can be compared against
  a URL (which requires that the traffic for the route be HTTP based) such
  that multiple routes can be served using the same host name, each with a
  different path. Routers should match routes based on the most specific
  path to the least; however, this depends on the router implementation. The
  following table shows example routes and their accessibility:
  