dstiles - 8:12 pm on Jul 7, 2009 (gmt 0)

graeme_p - generally a site is built with specific dynamic processors in mind - ASP, PHP etc - and the file extensions will reflect this.

If you move to another server it is likely you will move to a similar processor (php to php) so the file extensions will remain the same, and that includes htm/l if it was built for, say, PHP with that extension. The primary problem, I would have thought, would arise where the site was never built using a dynamic processor: ie pure html code. In that case you'd be best off changing the processor's default file extension.

fishfinger - you don't need rewrite to process htm/l extensions on ASP. The switch is in IIS under Configuration, where you can specify which DLL processes which file extension. This is on a site basis, so any site on a virtual server can be handled that way.

If your web host isn't willing to change that it's unlikely they will install isapi_rewrite, which requires more work and more money.