anchor.diff:  	``` 
   	Where `APP-NAME` is the name of your app
   
  -1. Configure CF with the ports your app is listening on:
  +1. Configure <%= vars.product_short %> with the ports your app is listening on:
   
   	```
   	cf curl /v2/apps/APP-GUID -X PUT -d '{"ports": [PORT1, PORT2, PORT3...]}'. 
  
positive.code: 
  Before following the procedure to configure routing to your app on custom ports, you must have the following:
  
  * An app pushed to PCF that can listen on one or more custom ports. 
  * Routes for which you would like traffic forwarded to your app on custom ports. 
  	For example, if your app listens on two ports and you'd like clients to be able to send requests to both of them, create two routes. These can be from HTTP or TCP domains (see [Routes and Domains](./deploy-apps/routes-domains.html) for more info). E.g. foo.example.com and bar.example.com. In the following procedure, you will use API endpoints to map these routes to your app on the ports it is listening.
  
  ## <a id="procedure"></a> Procedure
  
  
negative.code: owner: Routing
  ---
  
  This topic describes how to configure <%= vars.first_product_name %> to route traffic to your apps listening on custom ports. 
  
  ## <a id="overview"></a> Overview
  
  By default, apps only receive requests on port 8080 for both HTTP and TCP routing, and so must be configured, or hard coded, to listen on this port. Configuring custom app ports allows developers to bring workloads onto <%= vars.product_short %> that listen on ports other than 8080. Here are some example use cases:
  
  * Serving web client requests on one port and offering stats/debug on another
  * Using TCP protocols that require multiple ports 
  * Running Docker images on <%= vars.product_short %> 
  
  The [Procedure](#procedure) below describes how to use the `apps` and `route_mappings` Cloud Controller API endpoints to update the ports the app can receive requests on. 
  
  