IIS 5/6 .cfm files don"t work

I used to have a web site that was developed by an old employee. We hosted
it on IIS 5 on windows 2000 server. When I recently installed Server 2003
with IIS 6 and copied the files over, the site doesn't work. It doesn't
read the .cfm files. If I change the ext to .htm it will work, but the
flash coding is linking to .cfm files and I can't fix.

I have read that installing Coldfusion on the server will fix it, but I
don't want to pay 1500 for software we're not going to use. Any ideas how
to get IIS6 to recognize the files?

John

Re: IIS 5/6 .cfm files don"t work

On Dec 21, 11:54=A0am, "John Branton" wrote:
> I used to have a web site that was developed by an old employee. =A0We hos=
ted
> it on IIS 5 on windows 2000 server. =A0When I recently installed Server 20=
03
> with IIS 6 and copied the files over, the site doesn't work. =A0It doesn't=

> read the .cfm files. =A0If I change the ext to .htm it will work, but the
> flash coding is linking to .cfm files and I can't fix.
>
> I have read that installing Coldfusion on the server will fix it, but I
> don't want to pay 1500 for software we're not going to use. =A0 Any ideas =
how
> to get IIS6 to recognize the files?
>
> John


You must install Cold Fusion on a server for it to recognize and
process .cfm files. No way around it. You can blame the old employee
for this, not IIS. If you don't want to pay, then you need to write
web pages based on free platforms.

You will either need to buy Cold Fusion and attempt to migrate the old
website by hand, or rewrite it all in something that is freely
available on Windows/IIS, like ASP, ASP.Net, PHP, Perl.

By default, IIS only recognizes:
1. Static files that require no server-side processing. i.e. gif/jpg
files, html/xml files, css files
2. Dynamic files in the form of CGI EXE or ISAPI DLL
3. Script files which require either a CGI or ISAPI to process. i.e.
asp/aspx/php/pl files

ASP DLL comes with IIS. ASP.Net ISAPI DLL can be freely installed from
dotnetfx.exe. Likewise for PHP/Perl.

Cold Fusion is a type of #3 file. It requires the Cold Fusion ISAPI to
process. You have to purchase Cold Fusion to get the ISAPI DLL and its
configuration.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: IIS 5/6 .cfm files don"t work

Thanks for the information. The old employee didn't have any code running
on the pages except basic html he just named them .cfm because he migrated
another site that was cold fusion to basic html. The pages will function
fine if I change the name to .html with no problem, but the links in the
flash that was developed points to .cfm.

The old 2000 server didn't have cold fusion installed on it either that is
what is confusing me. The pages run when called on the old server as .cfm.

Any thoughts?

"David Wang" wrote in message
news:5dbbe4a7-5a10-430e-bb3d-e40ec9780ff2@i29g2000prf.google groups.com...
On Dec 21, 11:54 am, "John Branton" wrote:
> I used to have a web site that was developed by an old employee. We hosted
> it on IIS 5 on windows 2000 server. When I recently installed Server 2003
> with IIS 6 and copied the files over, the site doesn't work. It doesn't
> read the .cfm files. If I change the ext to .htm it will work, but the
> flash coding is linking to .cfm files and I can't fix.
>
> I have read that installing Coldfusion on the server will fix it, but I
> don't want to pay 1500 for software we're not going to use. Any ideas how
> to get IIS6 to recognize the files?
>
> John


You must install Cold Fusion on a server for it to recognize and
process .cfm files. No way around it. You can blame the old employee
for this, not IIS. If you don't want to pay, then you need to write
web pages based on free platforms.

You will either need to buy Cold Fusion and attempt to migrate the old
website by hand, or rewrite it all in something that is freely
available on Windows/IIS, like ASP, ASP.Net, PHP, Perl.

By default, IIS only recognizes:
1. Static files that require no server-side processing. i.e. gif/jpg
files, html/xml files, css files
2. Dynamic files in the form of CGI EXE or ISAPI DLL
3. Script files which require either a CGI or ISAPI to process. i.e.
asp/aspx/php/pl files

ASP DLL comes with IIS. ASP.Net ISAPI DLL can be freely installed from
dotnetfx.exe. Likewise for PHP/Perl.

Cold Fusion is a type of #3 file. It requires the Cold Fusion ISAPI to
process. You have to purchase Cold Fusion to get the ISAPI DLL and its
configuration.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: IIS 5/6 .cfm files don"t work

If the cfm-files are just pure html, create a mime type for .cfm and
configure it the same as .htm and it should start working.

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


"John Branton" skrev i meddelandet
news:u%23WNRWRRIHA.5016@TK2MSFTNGP06.phx.gbl...
> Thanks for the information. The old employee didn't have any code running
> on the pages except basic html he just named them .cfm because he migrated
> another site that was cold fusion to basic html. The pages will function
> fine if I change the name to .html with no problem, but the links in the
> flash that was developed points to .cfm.
>
> The old 2000 server didn't have cold fusion installed on it either that is
> what is confusing me. The pages run when called on the old server as .cfm.
>
> Any thoughts?
>
> "David Wang" wrote in message
> news:5dbbe4a7-5a10-430e-bb3d-e40ec9780ff2@i29g2000prf.google groups.com...
> On Dec 21, 11:54 am, "John Branton" wrote:
>> I used to have a web site that was developed by an old employee. We
>> hosted
>> it on IIS 5 on windows 2000 server. When I recently installed Server 2003
>> with IIS 6 and copied the files over, the site doesn't work. It doesn't
>> read the .cfm files. If I change the ext to .htm it will work, but the
>> flash coding is linking to .cfm files and I can't fix.
>>
>> I have read that installing Coldfusion on the server will fix it, but I
>> don't want to pay 1500 for software we're not going to use. Any ideas how
>> to get IIS6 to recognize the files?
>>
>> John
>
>
> You must install Cold Fusion on a server for it to recognize and
> process .cfm files. No way around it. You can blame the old employee
> for this, not IIS. If you don't want to pay, then you need to write
> web pages based on free platforms.
>
> You will either need to buy Cold Fusion and attempt to migrate the old
> website by hand, or rewrite it all in something that is freely
> available on Windows/IIS, like ASP, ASP.Net, PHP, Perl.
>
> By default, IIS only recognizes:
> 1. Static files that require no server-side processing. i.e. gif/jpg
> files, html/xml files, css files
> 2. Dynamic files in the form of CGI EXE or ISAPI DLL
> 3. Script files which require either a CGI or ISAPI to process. i.e.
> asp/aspx/php/pl files
>
> ASP DLL comes with IIS. ASP.Net ISAPI DLL can be freely installed from
> dotnetfx.exe. Likewise for PHP/Perl.
>
> Cold Fusion is a type of #3 file. It requires the Cold Fusion ISAPI to
> process. You have to purchase Cold Fusion to get the ISAPI DLL and its
> configuration.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>

Re: IIS 5/6 .cfm files don"t work

If the pages are just named .cfm for legacy reasons and do not require
Cold Fusion processing at all, then simply add a MIME Type at the
website-level for .cfm that looks like "text/html" and it should work.

FYI: Pages don't really "run" -- based on my prior taxonomy of the
requests that IIS recognizes, pages are either:
1. Static File - sent as-is to web browser as download. Browser
figures out what to do with it based on Content-Type (which is
controlled by MIME Type configuration on the server)
2. Dynamic File - CGI EXE and ISAPI DLL directly execute on the server
to generate a response to the client. You can view this as a dynamic
way to generate a "static file" back to the client because that's all
the browser sees.
3. Script File - pseudo language processed by CGI EXE or ISAPI DLL to
generate a response to the client as in #2

As you can see, everything you do on IIS reduces to #1 -- sending a
response back to the client. IIS never runs any pages. It only opens a
file and sends it back, or uses another DLL/EXE as script engine to
process the page and send back the same static response.

Thus, you just need to determine for your pages which one of the above
three categories they belong in, and configure accordingly. Sounds
like you use .cfm like .html as a static file, so you should configure
for #1.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On Dec 22, 7:40=A0pm, "John Branton" wrote:
> Thanks for the information. =A0The old employee didn't have any code runni=
ng
> on the pages except basic html he just named them .cfm because he migrated=

> another site that was cold fusion to basic html. =A0 The pages will functi=
on
> fine if I change the name to .html with no problem, but the links in the
> flash that was developed points to .cfm.
>
> The old 2000 server didn't have cold fusion installed on it either that is=

> what is confusing me. The pages run when called on the old server as .cfm.=

>
> Any thoughts?
>
> "David Wang" wrote in message
>
> news:5dbbe4a7-5a10-430e-bb3d-e40ec9780ff2@i29g2000prf.google groups.com...
> On Dec 21, 11:54 am, "John Branton" wrote:
>
> > I used to have a web site that was developed by an old employee. We host=
ed
> > it on IIS 5 on windows 2000 server. When I recently installed Server 200=
3
> > with IIS 6 and copied the files over, the site doesn't work. It doesn't
> > read the .cfm files. If I change the ext to .htm it will work, but the
> > flash coding is linking to .cfm files and I can't fix.
>
> > I have read that installing Coldfusion on the server will fix it, but I
> > don't want to pay 1500 for software we're not going to use. Any ideas ho=
w
> > to get IIS6 to recognize the files?
>
> > John
>
> You must install Cold Fusion on a server for it to recognize and
> process .cfm files. No way around it. You can blame the old employee
> for this, not IIS. If you don't want to pay, then you need to write
> web pages based on free platforms.
>
> You will either need to buy Cold Fusion and attempt to migrate the old
> website by hand, or rewrite it all in something that is freely
> available on Windows/IIS, like ASP, ASP.Net, PHP, Perl.
>
> By default, IIS only recognizes:
> 1. Static files that require no server-side processing. i.e. gif/jpg
> files, html/xml files, css files
> 2. Dynamic files in the form of CGI EXE or ISAPI DLL
> 3. Script files which require either a CGI or ISAPI to process. i.e.
> asp/aspx/php/pl files
>
> ASP DLL comes with IIS. ASP.Net ISAPI DLL can be freely installed from
> dotnetfx.exe. Likewise for PHP/Perl.
>
> Cold Fusion is a type of #3 file. It requires the Cold Fusion ISAPI to
> process. You have to purchase Cold Fusion to get the ISAPI DLL and its
> configuration.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //