Here is an example of the typical sequence for a request processed using a reverse proxy server.
For this example, for a Studio application, the request URL might be something like http://mystudio/eid/web/myapp, using the default port 80.
The hostname resolves to the address of the reverse proxy server. The reverse proxy is listening on this address and receives the request.
A reverse proxy might use any part of the URL to route the request, such as the protocol, host, port, path, or query-string. Typically the path is the main data used for routing.
The reverse proxy configuration rules determine the outbound URL to send the request to. This destination is usually the end server responsible for serving the content. The reverse proxy server may also rewrite parts of the request. For example, it may change or make additions to path segments.
Reverse proxies can also add standard or custom headers to the request.