anchor.diff:  $ cf create-route my-space foo.<%=vars.private_app_domain%>
   Creating route foo.<%=vars.private_app_domain%> for org my-org / space my-space as username<span>@</span>example.com...
   OK
  -
   </pre>
   
   Assuming DNS has been configured for this subdomain, this command instructs <%=vars.product_short%> to route requests to apps mapped to this route from the following URLs:
  
positive.code: $ cf create-route tcp.<%=vars.app_domain%> --port 60035
  Creating route tcp.<%=vars.app_domain%>:60035 for org my-org / space my-space as user@example.com...
  OK
  
  </pre>
  
  ### <a id='list-routes'></a>List Routes ###
  
negative.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. After this, the following occurs:
  
  - <%=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.
  