I'm using ARR 2.5 with IIS 7.5 on Server 2008 R2.
I'm trying to replace an existing squid proxy which acts as a reverse proxy in front of 2 IIS servers:
- squid forwards requests to serverA if the incoming url has a path that starts with /special/
- squid forwards any other request to serverB
- there are many different hosts
To be specific, the squid config looks like this:
*************
acl special urlpath_regex ^/special/
cache_peer serverA parent 80 0 no-query login=PASS originserver name=serverApeer
cache_peer_access serverApeer allow special
cache_peer_access serverApeer deny all
cache_peer serverB parent 80 0 no-query login=PASS originserver name=serverBpeer
cache_peer_access serverBpeer deny special
*************
The key bit is that when squid gets the incoming request and there's a cache miss, it makes the same request (same url) to the appropriate server behind it. Both serverA and serverB respond to the same request hosts, squid is just 'merging' their 'url space' via the path acl and cache_peer_access rules.
From what I've read so far, it looks like (but I haven't tested) that I might be able to get ARR to have the same effect by installing the ARR Helper module on serverA and serverB, and then it can 'undo' the url rewrite that happened when ARR forwarded the request. However, I'm trying to avoid using that module if possible since the existing squid reverse proxy is 'transparent' to those 2 backend servers (the URL request sent to them from squid is the same as what the client send to squid).
Is this type of 'pass through request' (no modification of the url) possible with ARR? Is it a bad fit and a better fit for replacing this kind of squid proxy would be something different (ISA as reverse proxy?)
If using ARR, would it be better to have serverA and serverB as separately defined server farms rather than 2 servers within a single server farm? it seems like the servers within a given server farm should normally be homogenous in terms of what url's they respond to, which isn't the case here.
Thanks!
I'm trying to replace an existing squid proxy which acts as a reverse proxy in front of 2 IIS servers:
- squid forwards requests to serverA if the incoming url has a path that starts with /special/
- squid forwards any other request to serverB
- there are many different hosts
To be specific, the squid config looks like this:
*************
acl special urlpath_regex ^/special/
cache_peer serverA parent 80 0 no-query login=PASS originserver name=serverApeer
cache_peer_access serverApeer allow special
cache_peer_access serverApeer deny all
cache_peer serverB parent 80 0 no-query login=PASS originserver name=serverBpeer
cache_peer_access serverBpeer deny special
*************
The key bit is that when squid gets the incoming request and there's a cache miss, it makes the same request (same url) to the appropriate server behind it. Both serverA and serverB respond to the same request hosts, squid is just 'merging' their 'url space' via the path acl and cache_peer_access rules.
From what I've read so far, it looks like (but I haven't tested) that I might be able to get ARR to have the same effect by installing the ARR Helper module on serverA and serverB, and then it can 'undo' the url rewrite that happened when ARR forwarded the request. However, I'm trying to avoid using that module if possible since the existing squid reverse proxy is 'transparent' to those 2 backend servers (the URL request sent to them from squid is the same as what the client send to squid).
Is this type of 'pass through request' (no modification of the url) possible with ARR? Is it a bad fit and a better fit for replacing this kind of squid proxy would be something different (ISA as reverse proxy?)
If using ARR, would it be better to have serverA and serverB as separately defined server farms rather than 2 servers within a single server farm? it seems like the servers within a given server farm should normally be homogenous in terms of what url's they respond to, which isn't the case here.
Thanks!