-
Posted to
IIS 7.0 - Application Request Routing (ARR)
by
Rolle
on
07-20-2009, 11:36 AM
Great! It's working on our dev area...
Thanks!
-
Posted to
IIS 7.0 - Application Request Routing (ARR)
by
Rolle
on
04-15-2009, 4:36 AM
Another scenario I have been able to reproduce this problem in, is as follows:
Using a squid proxy for example and disabling the client IP forwarding, the proxy sets the X-Forwarded-For to unknown in the request header. The load balancer then sends the IP of the requesting proxy and if set the value of the X-Forwarded-For in the request header ...
-
Posted to
IIS 7.0 - Application Request Routing (ARR)
by
Rolle
on
04-14-2009, 12:35 PM
Hi,
I know that the client IP should always be passed and thats why this is quite interesting. Some requests to the Loadbalancer are passed directly to the Backend IIS Servers, this is due to the current rebuild of the system that we are in at the moment. Due to this I started a Trace and found Requests coming from upstream Proxies directly to ...
-
Posted to
IIS 7.0 - Application Request Routing (ARR)
by
Rolle
on
04-13-2009, 12:04 PM
Hi,
The ARR Helper Module is just what I was looking for to replace an old ISAPI Filter.
While testing the module on our development system (IIS 7) I have come across a problem.
When using the X-Forwarded-For functionality to capture the client IP from the Loadbalancer all is well as long as the entered value from the Loadbalancer is a valid IP, ...