tedster - 10:54 pm on Nov 13, 2006 (gmt 0)

If that was the case, every IIS server in the world would have dup content issues

I work with many IIS sites, and it is true that they have this increased liability for duplicate URLs. If the developers are disciplined about capitalization throughout their mark-up, and there are few to no capitalization oddities in their IBLs from other domains, then the dup content issues may be minimal.

But the issue are often there -- 80% of the time I'd say. Microsoft's server tends to encourage a certain lack of discpline in this area. I almost always find at least some of this trouble when companies bring me an already developed site served on IIS.

The best practice I have found is to use all lower case for html files names -- and forget the cutsie CamelCase thing. A rewrite utility such as ISAPIrewrite can go miles to fix any damage.

.NET sites on IIS have three or four liabilities that are as common as termites in old Goergia homes. The so-called "custom 404" that actually returns a 302 status is another common source of Supplemental URLs for .NET/IIS websites.