anchor.diff:  
   Applications can communicate without leaving the platform on the container network using internal routes. An internal route can be created using the [map-route](#map-internal-route) command with an [internal domain](#internal-domains).
   
  -By default, apps cannot communicate with each other on the container network. In order for an app to talk to another app a [network policy](http://cli.cloudfoundry.org/en-US/cf/add-network-policy.html) must be created.
  +By default, apps cannot communicate with each other on the container network. In order for an app to talk to another app a [network policy](https://cli.cloudfoundry.org/en-US/cf/add-network-policy.html) must be created.
   
   ### <a id='create-route'></a>Create a Route ###
   
   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 an 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.
  +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](https://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.
   
   #### <a id='create-route-with-hostname'></a>Create an HTTP Route with Hostname ####
   
  -In <%=vars.product_short%>, a hostname is the label that indicates a subdomain of the domain associated with the route. Given a domain `<%=vars.app_domain%>`, a developer can create the route `myapp.<%=vars.app_domain%>` in space `my-space` by specifying the hostname `myapp` with the [cf create-route](http://cli.cloudfoundry.org/en-US/cf/create-route.html) command as shown in this example:
  +In <%=vars.product_short%>, a hostname is the label that indicates a subdomain of the domain associated with the route. Given a domain `<%=vars.app_domain%>`, a developer can create the route `myapp.<%=vars.app_domain%>` in space `my-space` by specifying the hostname `myapp` with the [cf create-route](https://cli.cloudfoundry.org/en-US/cf/create-route.html) command as shown in this example:
   
   <pre class="terminal">
   $ cf create-route my-space <%=vars.app_domain%> --hostname myapp
  
positive.code: 
  ### <a id='map-route'></a>Map a Route to Your Application ###
  
  For an app to receive requests to a route, developers must map the route to the app with the [cf map-route](http://cli.cloudfoundry.org/en-US/cf/map-route.html) command. If the route does not already exist, this command creates it.
  
  <p class="note"><strong>Note</strong>: Any app that is not routed to port <code>80</code> or port <code>443</code> must be explicitly mapped using the <code>cf map-route</code> command . Otherwise, the route is automatically mapped to port <code>443</code>.
  </p>
  
negative.code: 
  ### <a id='list-routes'></a>List Routes ###
  
  Developers can list routes for the current space with the [cf routes](https://cli.cloudfoundry.org/en-US/cf/routes.html) command. A route is uniquely identified by the combination of hostname, domain, port, and path.
  
  <pre class="terminal">
  $ cf routes
  