Skip to content

Commit ee0b926

Browse files
committed
adds table and diagram describing flow of traffic[#162459151]
1 parent 2886b99 commit ee0b926

File tree

2 files changed

+31
-0
lines changed

2 files changed

+31
-0
lines changed

custom-ports.html.md.erb

+31
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,37 @@ By default, apps only receive requests on port 8080 for both HTTP and TCP routin
1717

1818
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.
1919

20+
### <a id="flow"></a> Flow of a Request to an App
21+
22+
The following table describes the types of ports used at each stage of a client request. The procedure in this document discusses configuring _app ports_ specifically.
23+
24+
<table>
25+
<tr>
26+
<th>Port Type</th>
27+
<th>Description</th>
28+
<th>Applicable Stage</th>
29+
</tr>
30+
<tr>
31+
<td>Route port</td>
32+
<td>The port a client sends a request to</td>
33+
<td>Client to load balancer, load balancer to Gorouter</td>
34+
</tr>
35+
<tr>
36+
<td>Backend port</td>
37+
<td>The port of the host VM where an app container is hosted</td>
38+
<td>Gorouter to Diego Cell</td>
39+
</tr>
40+
<tr>
41+
<td>App port</td>
42+
<td>The port on which the app listens for requests</td>
43+
<td>Diego Cell to app container</td>
44+
</tr>
45+
</table>
46+
47+
See the following diagram for an illustration of a request using example routes and ports.
48+
49+
![Traffic-flow-diagram](route_ports.png)
50+
2051
## <a id="prerequisite"></a> Prerequisite
2152

2253
Before following the procedure to configure routing to your app on custom ports, you must have the following:

images/route_ports.png

8.58 KB
Loading

0 commit comments

Comments
 (0)