ARR Request cannot be routed because it has reached the Max-Forwards limit. The server can independently refer to the request routing topology

I have two standard Windows 2008 R2 servers that have IIS 7.5 installed (Server1 and Server2). On Server1, I installed Web Farm Framework 2.2 and created the server farm "myFarm.com". I also installed ARR on Server1.

In the server farm, I added Server2 and Server1 as secondary servers. I configured ARR with the default setting. The load balancing is set to "Round Robin" so that the request can go to both servers randomly.

To test my setup, I created the Test.ASPX page and deployed it to both servers. This is a simple page that returns the server_name on which the server page runs. That way, I would know that load balancing works or not.

Then I opened Internet Exlorer and tried to view my Test.ASPX page from server1, which hosts the web farm and ARR. Every time I click on a page request, it only goes to Server2. I made my server2 unhealthy in webfarm to check if Server1 is processing the request or not. When I tried to click Test.aspx in the browser, I was surprised to add the following error:

The request cannot be routed because it has reached the Max-Forwards limit. The server can independently refer to the request routing topology.

, 2 , ARR Server1, , loopback. .

, , , Server1 -, ARR, , ARR.

, 2 2.

- , ?

+5
2

ARR max-fowards, ARR 80 - : ex 8080

, ARR , , .

: -)

+3

, , ( , ).

, :

  • - Server2, , 88 (.. , http://Server2:88/Test.ASPX).
  • ( β†’ URL Rewrite), , 88:

URL rewrite configuration

+3

All Articles