File Extensions - something other than .cfm

[mathandmetal]

I've run into a good number of MSIE flavors which simply refuse correctly honor
the MIME type, and so mapping different extensions to run CF code on the server
has been a life-savor here.

And
[url]http://livedocs.macromedia.com/coldfusion/5.0/Installing_and_Configuring_ColdFus[/url]
ion_Server/wininstall5.htm worked fine on Windows NT to 2000.

But I just upgraded to MX and Windows 2003. Following the same basic steps is
just not working. If I figure it out I'll post, but if anyone else has figured
this out for MX & W2003, sharing would be great!

[v_roma]

HIH,
You can do this by changing some settings on your IIS server, if that's what
you're using. See the following note (it's for versions 5 and prior but it
might work for newer versions too):

[url]http://www.macromedia.com/go/tn_18214[/url]

I have just tried this (I'm using CF 5.0) and it worked, though not the way I
wanted it too. I wanted CF to run the application template every time someone
requested a non-cfm file on my web site. I basically wanted to prevent users
from circumventing my application-based login by typing the full address to the
non-cfm file. But what this does instead, and I should've seen it coming, is
to try to process the file as if it were a cfm file. So the server will be
looking for cfm code in your pdf, xls, etc files, which results in very ugly
errors, as you can imagine. It's too bad because I wanted to avoid the whole
CFCONTENT nonsense. Does anyone know of any way to call the application
template when a non-cfm file is requested without having CF try to parse the
non-cfm file?

I've been researching this for ages and have yet to find a solution that
doesn't involve CFCONTENT.

Thanks,
v_roma