anchor.diff:  
   <pre class="terminal">
   $ 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%>`.
  
positive.code: 
  This approach creates a route with the same address as the domain itself and is permitted for private domains only. For more information, see the [Private Domains](#private-domains) section.
  
  A developer can create a route in space `my-space` from the domain `<%=vars.private_app_domain%>` with no hostname with the following command:
  
  <pre class="terminal">
  $ cf create-route my-space <%=vars.private_app_domain%>
  </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: 
  
negative.code: 
  When a developer creates a route using the cf CLI, <%=vars.product_short%> determines whether the route is an HTTP or a TCP route based on the domain. To create a HTTP route, a developer must choose a HTTP domain. To create a TCP route, a developer must choose a TCP domain.
  
  Domains in <%=vars.product_short%> provide a namespace from which to create routes. To list available domains for a targeted organization, use the [cf domains](http://cli.cloudfoundry.org/en-US/cf/domains.html) command. For more information about domains, see the <a href="#domains">Domains</a> section. 
  
  The following sections describe how developers can create HTTP and TCP routes for different use cases.
  
  