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: 
  The <%=vars.product_short%> Gorouter routes requests to applications by associating 
  an app with an address, known as a route. We call this association a **mapping**. 
  Use the cf CLI [cf map-route](http://cli.cloudfoundry.org/en-US/cf/map-route.html) 
  command to associate an app and route.
  
  The routing tier compares each request with a list of all the routes mapped to apps 
  
negative.code: 
  The routing tier knows the location of instances for apps mapped to routes. Once the routing tier determines a route as the best match for a request, it makes a load-balancing calculation using a round-robin algorithm, and forwards the request to an instance of the mapped app.
  
  Developers can map many apps to a single route, resulting in load-balanced requests for the route across all instances of all mapped apps. This approach enables the blue/green zero-downtime deployment strategy. Developers can also map an individual app to multiple routes, enabling access to the app from many URLs. The number of routes that can be mapped to each app is approximately 1000 (128KB). 
  
  Routes belong to a space, and developers can only map apps to a route in the same space.
  
  