anchor.diff:  $ cf push tcp-app -d <%=vars.tcp_app_domain%> --random-route
   </pre>
   
  -#### <a id='map-route-with-manifest'></a>Map a Route Using Application Manifest ####
  +#### <a id='map-route-with-manifest'></a> Map a Route Using Application Manifest
   
   Developers can map a route to their app with a manifest by editing the `route` attribute to specify the host, domain, port and/or path components of the route. For more information, see the [Deploying with Application Manifests](../deploy-apps/manifest.html#routes) topic.
   
  -#### <a id='map-route-to-multiple-apps'></a>Map a Route to Multiple Apps ####
  +#### <a id='map-route-to-multiple-apps'></a> Map a Route to Multiple Apps
   
   <%= partial 'routing_conflict' %>
   
   See the [Routing Conflict](./troubleshoot-app-health.html#routing-conflict) section of the Troubleshooting Application Deployment and Health topic for more information about troubleshooting this problem.
   
  -#### <a id='map-multiple-routes'></a>Map Multiple Routes to One App ####
  +#### <a id='map-multiple-routes'></a> Map Multiple Routes to One App
   
   You can have multiple routes to an app, but those routes cannot have different context paths.
   
  
positive.code: $ cf map-route myapp apps.internal --hostname foo
  </pre>
  
  ### <a id='unmap-route'></a>Unmap a Route ###
  
  Developers can remove a route from an app using the `cf unmap-route` command. The route remains reserved for later use in the space where it was created until the route is deleted.
  
  
negative.code: $ cf map-route myfallbackapp foo.<%=vars.app_domain%> --hostname '*'
  </pre>
  
  #### <a id='map-route-on-push'></a> Map a Route with Application Push
  
  Developers can map a route to their app with the `cf push` command.
  
  