anchor.diff:  
   space      host     domain               path        apps
   my-space   myapp    <%=vars.app_domain%>                myapp
  -my-space   myapp2   <%=vars.app_domain%>                myapp
  -my-space   foo      <%=vars.private_app_domain%>               myapp
  +my-space   myapp    <%=vars.private_app_domain%>               myapp
   my-space   store    <%=vars.app_domain%>    /products   products
   my-space   store    <%=vars.app_domain%>    /orders     orders
   my-space   store    <%=vars.app_domain%>                storefront
  
positive.code: To create a wildcard route submit an asterix for the hostname.
  
  <pre class="terminal">
  $ cf create-route my-space foo.<%=vars.app_domain%> -n *
  </pre>
  
  An application mapped to a wildcard route acts as a fallback app for route requests if the requested route does not exist. For example, if a client sends a request to `http://app.foo.<%=vars.app_domain%>` by accident, meaning to reach `myapp.foo.<%=vars.app_domain%>`, the request will be routed to the application mapped to the route `*.foo.<%=vars.app_domain%>`.
  
  #### <a id='create-route-with-path'></a>Create a Route with a Path####
  
  To create a route for a host with a path.
  
  <pre class="terminal">
  $ cf create-route my-space <%=vars.app_domain%> -n myapp --path mypath
  </pre>
  
  This creates a route in space `my-space` from domain `<%=vars.app_domain%>` with hostname `myapp` and path `mypath`.
  
  <p class="note"><strong>Note</strong>: You cannot create a route with the same host and domain, but a different path, in another space.</p>
  
  For example, assuming there are three applications deployed (`products`, `orders` and `storefront`) and following routes are created:
  
  <pre class="terminal">
  $ cf create-route my-space <%=vars.app_domain%> -n store --path products
  $ cf create-route my-space <%=vars.app_domain%> -n store --path orders
  $ cf create-route my-space <%=vars.app_domain%> -n store
  </pre>
  
  If the first route is associated to the `products` app, the second route to the `orders` app and the last route to the `storefront` app:
  
  Requests to `http://store.<%=vars.app_domain%>/products` will be routed to the `products` app
  Requests to `http://store.<%=vars.app_domain%>/orders` will be routed to the `orders` app
  Requests to `http://store.<%=vars.app_domain%>` will be routed to the `storefront` app
  
  Routes with a path will be attempted to be matched on first and then attempt to match on host and domain.
  
  <p class="note"><strong>Note</strong>: A route with a path does NOT map to the root context of an application, meaning that the app that is associated to a route with a path must be able to respond to that path.</p>
  
  
  ### <a id='list-routes'></a>List Routes ###
  
  You can list routes for the current space with the `cf routes` command. A route is uniquely identified by the combination of host and domain.
  
  <pre class="terminal">
  $ cf routes
  
negative.code: 	</tr>
  </table>
  
  The commands below will map the above routes to their respective apps. Hostname, domain, and path are used to uniquely identify a route to map an application to.
  
  <pre class="terminal">
  $ cf map-route products <%=vars.app_domain%> --hostname store --path products
  $ cf map-route orders <%=vars.app_domain%> --hostname store --path orders
  $ cf map-route storefront <%=vars.app_domain%> --hostname store
  </pre>
  
  The command below maps the wildcard route `*.foo.<%=vars.app_domain%>` to the application `myfallbackapp`.
  
  <pre class="terminal">
  $ cf map-route myfallbackapp foo.<%=vars.app_domain%> --hostname *
  </pre>
  
  #### <a id='map-route-on-push'></a>Map a Route with Application Push ####
  