Won Yoo's Blog

In this blog, I will not discuss what ETag is or whether I agree with some of the articles that have written around whether the use of ETag is a good or a bad idea.

One of the areas that we have optimized in IIS 8.0 beta is IIS configuration system.   There are many improvements that we have made in this area, but there is one simple change that has yielded a great result.   The change has not only improved the performance of IIS configuration system, but it has also helped with serving contents faster, especially when the contents are stored in a remote file server, by minimizing the "chattiness" between IIS and the file server.

I've noticed that some customers use Application Request Routing (ARR) to load balance between multiple sites that run on the same Windows/IIS instance.   For example, ARR may be listening on port 80, and it load balances the requests between 3 sites that listen on port 8080, 8081 and 8082 on the same ARR server.

This is "simple", yet it is definitely one of my favorite features in IIS 8.0 beta.

Windows Sever 8 beta was released yesterday and I am excited to write about some of the key features for web hosters and service providers.  

I am excited for our customers to finally download Windows Server 8 beta and see what we have been working on. 

Note: The content of this post is outdated. Please refer to the new post at http://blogs.iis.net/erez/archive/2013/11/27/installing-arr-manually-without-webpi.aspx for updated info and links. 

It is pretty common to run ARR as a proxy behind another proxy in a corporate environment and I've been asked how ARR can be configured in such an environment.   This practice is also known as "proxy chaining" where one proxy is "chained" to another proxy.