-
Posted to
IIS 7.0 - Application Request Routing (ARR)
by
himanshp
on
10-07-2009, 4:31 PM
Thanks James for sending freb logs.
Kernel cache was disabled by URL Rewriter Rule and that was because of using {HTTPS} server variable in rule. This issue is now fixed. Next version of URL Rewriter will have this fix.
For the workaround you can remove {HTTPS} server variable and use {CACHE_URL} and match pattern to "https:*" ...
-
Posted to
IIS7 - URL Rewrite Module
by
himanshp
on
10-06-2009, 2:37 PM
Hi Dean,
If I understand this correctly what you are trying to do is to redirect http/https requests to https://host/owa. To do that from your rules first rule looks good but you need to change second rule. You rules might look like as below
<rule ...
-
Posted to
IIS 7.0 - Application Request Routing (ARR)
by
himanshp
on
09-30-2009, 7:54 PM
Hi Jim,
You can just enable FREB log for 200 status code and collect freb log htm page ( less then 256 KB ) which is not already cached ( in disk/memory). When you enable FREB log make sure that you add ( ARR and URL Rewriter) providers. Also can you check what server variables you are using in rewriter rules?
Thanks
Himanshu
-
Posted to
IIS 7.0 - Application Request Routing (ARR)
by
himanshp
on
09-30-2009, 3:51 PM
Changing default cache duration shoud now cache for 60 seconds in memory. I just tried it and it works in my machine.
Can you please check few things?
1. What is your "Response Buffer Threshold Value"?
2. If you are using any URL independent server variable then URL rewriter will disable kernel cache. How do your rewriter rules look ...
-
Posted to
IIS 7.0 - Application Request Routing (ARR)
by
himanshp
on
09-30-2009, 2:31 PM
You can create 2 websites with different port binding. And you can create 2 server farms and add appropriate servers in each server farm. Now you can use url rewriter rules to forward traffic to correct server farm based on port number.
For Example: I have 2 server farms, serverFarm1 and serverFarm2 and I want to forward all the requests to ...
-
Posted to
IIS7 - URL Rewrite Module
by
himanshp
on
09-25-2009, 4:04 PM
Hi Dean,
I am not able to understand your scenario above. Your both rules looks same from "condition" perspactive because in both rules you are checking for {HTTPS} is "off". Because of this your second rule will never get executed if if {HTTPS} is "off".
Can you please explain your scenario ...
-
Posted to
IIS7 - URL Rewrite Module
by
himanshp
on
09-25-2009, 12:55 PM
Hi TJ,
Good to know that above configuration is working. BTW trackallcapture should work if you have URL Rewriter V2 Beta version installed. Let me know if you are trying to achieve specific scenarios and need help in it.
Also, ARR Version 2 Release Candidate is released yesterday. Check out feature list and documentation ...
-
Posted to
IIS7 - URL Rewrite Module
by
himanshp
on
09-24-2009, 5:52 PM
Hi TJJones,
One of the simple solutions is to create 2 server farms. And add one server in each server farm. Now create 2 url rewriter rules which will route to appropriate server farm based on Host header.
Here is how the rewriter rule and server farm will look ...
-
Posted to
IIS 7.0 - Application Request Routing (ARR)
by
himanshp
on
09-24-2009, 5:16 PM
Hi JAltrichter,
What you are seeing is expected. Disk health status is a RSCA counter, value of which is "UNKNOWN" when there is no workerprocess running. When server starts getting request ( will start wokkerprocess ) then that status will be updated to either "healthy" or "unhealthy".
Same is true for disk ...
-
Posted to
IIS 7.0 - Application Request Routing (ARR)
by
himanshp
on
09-21-2009, 12:38 PM
Hi Newkgb,
Are you opening InetMgr from MMC? If yes then this is known issue in beta which will be fixed in RC (Release Candidate) version (Previous thread). Workaround for this is open InetMgr on its own. Can you please try opening InetMgr directly and see it that solves your problem. If not can you please check event viewer and see if ...