anchor.diff:  ---
  -title: Configuring Apps to Listen on Custom Ports (Beta)
  +title: Configuring CF to Route Traffic to Apps on Custom Ports (Beta)
   owner: Routing
   ---
   
  -This topic describes how to configure your apps to listen for traffic on custom ports. 
  -
  -<p class="note"><strong>Note</strong>: This is a beta feature. Some of the API endpoints described in this topic are not yet considered generally available.</p>
  +This topic describes how to configure Cloud Foundry 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. Configuring custom app ports allows developers to bring workloads onto Cloud Foundry (CF) that listen on ports other than 8080. Here are some example use cases:
  +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 Cloud Foundry (CF) 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 
  
positive.code: 	</tr>
  	<tr>
  		<td>Backend port</td>
  		<td>The port of the host VM where an app container is hosted</td>
  		<td>Gorouter to Diego Cell</td>
  	</tr>
  	<tr>
  		<td>App port</td>
  		<td>The port on which the app listens for requests</td>
  		<td>Diego Cell to app container</td>
  	</tr>
  </table>
  
  See the following diagram for an illustration of a request using example routes and ports. 
  
  ![Traffic-flow-diagram](route_ports.png)
  
  
negative.code: 	``` 
  	Where `APP-NAME` is the name of your app
  
  1. Configure CF with the ports your app is listening on:
  
  	```
  	cf curl /v2/apps/APP-GUID -X PUT -d '{"ports": [PORT1, PORT2, PORT3...]}'. 
  