Skip to content

Commit 187e311

Browse files
committed
PR feedback
1 parent 4183f80 commit 187e311

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

support/developer/webapps/iis/application-request-routing/proxy-server-rejects-back-end-requests.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,14 +10,14 @@ ms.reviewer: paulboc, v-shaywood
1010

1111
# Proxy server rejects requests from ARR to back-end servers
1212

13-
This article provides troubleshooting guidance for a scenario in which a proxy server rejects requests that are directed through it from your Application Request Routing (ARR) server to back-end servers. In this scenario, the proxy server rejects the requests from ARR as incorrectly formatted.
13+
This article provides troubleshooting guidance for a scenario in which a proxy server is placed between an Application Request Routing (ARR) server and its back-end servers. The ARR server acts as a load balancer and the back-end servers comprise the ARR server farm that the ARR module is routing requests to. In this scenario, the proxy server might reject the requests from ARR as incorrectly formatted.
1414

1515
## Symptoms
1616

17-
When your ARR server routes a request to a back-end server that's on a different network, the request attempts to transits through a proxy server to reach the other network. When the request attempts to transit the request through the proxy server, the following events occur:
17+
When your ARR server routes a request to a back-end server that's on a different network, the request might have to transit through a proxy server to reach the other network. When the proxy server process the request to be routed to the back-end servers in the ARR farm, the following events might occur:
1818

1919
- The proxy server rejects the request and returns an `HTTP 400 Bad Request` status code with an error message that the requested URL is invalid.
20-
- The ARR server returns an `HTTP 400 Bad Request` status code and the following error message to the client that initiated the request:
20+
- When the ARR server receives the `HTTP 400 Bad Request` status code from the proxy server, it returns the same `HTTP 400 Bad Request` status code and the following error message to the client that initiated the request:
2121

2222
> Some aspect of the requested URL is incorrect.
2323
@@ -30,7 +30,7 @@ When your ARR server routes a request to a back-end server on the same network,
3030

3131
:::image type="content" source="./media/proxy-server-rejects-back-end-requests/normal-network-layout.png" alt-text="Network diagram of the typical ARR and back-end server configuration when on the same network":::
3232

33-
However, if your back-end server is on a different network than your ARR server, your ARR server might route requests to the back-end server through a proxy server. For example:
33+
However, if your back-end server is on a different network than your ARR server, your ARR server might have to route requests to the back-end server through a proxy server. For example:
3434

3535
:::image type="content" source="./media/proxy-server-rejects-back-end-requests/proxy-network-layout.png" alt-text="Network diagram of the ARR and back-end server configuration when on a different network, using a proxy server to transit request between networks":::
3636

0 commit comments

Comments
 (0)