anchor.diff:  $ cf create-route my-space <%=vars.private_app_domain%>
   Creating route <%=vars.private_app_domain%> for org my-org / space my-space as username<span>@</span>example.com...
   OK
  -
   </pre>
   
   If DNS has been configured correctly, this command instructs <%=vars.product_short%> to route requests to apps mapped to this route from the following URLs:
  
positive.code: $ cf create-route my-space <%=vars.app_domain%> --hostname store
  Creating route store.<%=vars.app_domain%> for org my-org / space my-space as username<span>@</span>example.com...
  OK
  
  </pre>
  
  The developer can then map the the new routes to different apps by following the steps in the <a href="#map-route">Map a Route to your Application</a> section below.
  
  If the developer maps the first route with path `products` to the `products` app, the second route with path `orders` to the `orders` app, and the last route to the `storefront` app, then:
  
  - <%=vars.product_short%> routes requests to `http://store.<%=vars.app_domain%>/products` to the `products` app.
  - <%=vars.product_short%> routes requests to `http://store.<%=vars.app_domain%>/orders` to the `orders` app.
  
negative.code: $ cf create-route my-space foo.<%=vars.app_domain%> --hostname *
  Creating route *.foo.<%=vars.app_domain%> for org my-org / space my-space as username<span>@</span>example.com...
  OK
  </pre>
  
  If a client sends a request to `http://app.foo.<%=vars.app_domain%>` by accident, attempting to reach `myapp.foo.<%=vars.app_domain%>`, <%=vars.product_short%> routes the request to the app mapped to the route `*.foo.<%=vars.app_domain%>`.
  