Beefing Up IIS: 10 Tips From A Former Solaris Admin - Tips 5 Down To 1 (Page 3 of 4 )
Tip 5: Gzip site content Browsers can handle Gzipped and deflated content and decompress it on the fly. While IIS 5 had a gzip feature built-in, it is pretty much broken. Enter products like PipeBoost to give us better functionality -- similar to what Apache users have enjoyed with mod_gzip. Don't waste your bandwidth -- even Google encodes its content, and their pages are tiny.
Tip 4: Cache your content While I'm on the topic of improving performance, remember to make your site cache friendly. You can set expiration headers for different files or directories right from the MMC. Just right click on an item via the IIS MMC, flip to the "HTTP Headers" tab, and away you go. If you want to set cache control headers programmatically -- or even better, let your site developers do it -- use something like CacheRight. If you want to go further and add reverse proxy caching, particularly for generated content, use a product like XCache -- which also throws in compression.
It might involve more time and expense to take full advantage of caching, but when you watch your logs shrink because they don't contain tons of pointless 304 responses, and your bandwidth consumption drop likes a stone -- even while your total page views increase over the same period -- you'll start to understand why this particular tip was so important. Cache friendly sites are quite rare, but there is plenty of information available online about the enormous benefits to be had by doing it right: Check out Brian Davidson's page, this nifty tutorial from Mark Nottingham. Tip 3: Tune your server Tuning IIS is no small topic -- whole books and courses are dedicated to it. But some good basic help is available online, such as this piece from IIS guru Brett Hill, or this knowledge Base article from Microsoft itself. However, if you don't feel like getting your hands dirty -- or can't afford the time and expense of turning yourself into an expert -- take a look at XTune, from the makers of XCache. It's performance tuning wizards step you through the process of tuning your IIS environment, making expert recommendations along the way.
Tip 2: Secure your server with simple fixes Sure, people are going to attack sites, but you don't have to be a sitting duck if you're willing to make even a small effort. First off, don't advertise the fact that you’re running IIS by showing your HTTP server header. Remove or replace it using something like ServerMask -- probably the best twenty-five bucks you'll ever spend. You can go further than this by removing unnecessary file extensions to further camouflage your server environment, and scanning request URLs for signs of exploits. There are number of commercial products that perform user input scanning, and Microsoft offers a free tool called URLScan which does the job. URLScan runs in conjunction with IISLockDown, a standard security package which should probably be installed on every IIS server on the planet. These are simple fixes that could pay off big, so do them now.
Tip 1: Patch, patch, patch! Okay, we in the IIS world do have to patch our systems and make hot fixes. However, as a former Solaris admin I had to do the same thing there, so I'm not sure why this is such a big surprise. You really need to keep up with the patches. Microsoft is of course the definitive source, but you can also use the highly-regarded www.cert.org. Simply search for "IIS".