Map IIS 8.5 / Coldfusion 11 to process .htm files same as .cfm files.

Have you modified the "uriworkermap.properties" file as well?

reference link:  http://www.webtrenches.com/post.cfm/processing-html-htm-or-other-files-in-coldfusion-10

Dan

Dan - That looked very promising but did not work for me. It may because I have another problem:

HTTP Error 500.0 - Internal Server Error

I get this whenever a ColdFusion module is run (.cfm) except when that file is the default document for the site.  

Example:

www.example.com  (if the default document residing in the site root has been defined as 'index.cfm' then the ColdFusion code is executed correctly. It makes no different which ColdFusion document it is, it runs fine.

But with the following example, it does not run correctly:

www.example.com/index.cfm  If it's a cfm file, it generates the Error 500. If its an .htm file, no error. If the .htm file has CF code, there is no error but the code is not executed, just seen as though a text file.

So, unless the .cfm file is the default document when run it generates the Error 500, no matter where the file is stored or which folder. Same is true of any links to a .cfm file.  

So, ColdFusion does work, at least with the default document so I'd think this idea should point to a clue for you experts. The Web.Config file looks fine. Application pool is set for Default-AppPool but I've tried different settings with the same result. The virtual directories were created when I used the Web Configuration Tool but there was an error during the process:

Error: < message: Cannot find requested collection element.
ERROR < message: New add object missing reqired attribute. Cannot add duplicate collection entry of type 'add' with unique key attribute 'name' set to cfrHandler'

The error did not seem to be fatal because the virtual directories were created, including /CFIDE.

Here's the web.config

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <defaultDocument>
            <files>
                <remove value="index.cfm" />
                <remove value="index.htm" />
                <remove value="default.aspx" />
                <remove value="iisstart.htm" />
                <remove value="index.html" />
                <remove value="Default.asp" />
                <remove value="Default.htm" />
                <add value="index.cfm" />
            </files>
        </defaultDocument>
    </system.webServer>
</configuration>

As you can see I removed the ReWrite Tool so as not to complicate the problem and better understand what's going on.

Does the Web Platform Installer in IIS need to be run, including Microsoft Azure Powershell and Cross-platform Command Line Tools? I just installed both but don't see any obvious options or changes.

Then there's the IIS 8 "Configuration Editor". I've not touched it. Do I need to do something with it?  Would be great to find some documentation there for "Build a Classic ColdFusion website on IIS." There are tons of options within that editor but where does one begin? This is so complicated without any guide for the basics to be sure everything is installed correctly and when those generic error code flash, they are not much help.  So, that's why I'm here, hoping and knowing probably I've missed some simple basic step. But which one out of the hundreds or perhaps thousands offered in a multitude of confusing hodgepodge files and categories!!

Maybe there's much more I should do to make the web.config file solve the problem but I don't have a clue and cannot find any good, fool-proof help on exactly what needs to be done to get ColdFusion 11 specifically working on IIS 8.5 and Windows 2012 Server r2. If you know of one and have no other suggestions, please forward me the link.

Can you post (or PM) the handler mapping you configured?

Dan

Dan - Handler mapping? Sure will but what is it? Where would I find it, in IIS 8 configuration, in a file somewhere?

You may be on the right track, not sure. I could not get it to work. I tried many different variation, script or execute, stopped and started cf each time but the general result is a variation of this error:

HTTP Error 404.17 - Not Found
The requested content appears to be script and will not be served by the static file handler.

Most likely causes:
The request matched a wildcard mime map. The request is mapped to the static file handler. If there were different pre-conditions, the request will map to a different handler.

Things you can try:
If you want to serve this content as a static file, add an explicit MIME map.

Detailed Error Information:
Module         StaticFileModule
Notification         ExecuteRequestHandler
Handler         StaticFile
Error Code         0x80070032
Requested URL       http://www.example.com:80/home.cfm
Physical Path              C:\server\server\home.cfm
Logon Method      Anonymous
Logon User             Anonymous


The domain info was substituted of course.

The main problem is getting ColdFusion modules to work correctly, not a CF problem but IIS 8.5.

So, let's put the problem of not being able to use .htm files containing cf code away as that's secondary. I could workaround that problem if I need to.

Again, if the default document is a cf file (.cfm) it executes correctly when just the domain or folder is given in the url as my example gave:

www.example.com  - Default document index.cfm runs fine. It makes no different which ColdFusion document it is, it runs fine if it is the default document but not shown in the URL or LINK.

But with the following example, the .cfm file does not run correctly:

www.example.com/index.cfm  If it's a cfm file, it generates the Error 500. If its an .htm file, no error. If the .htm file has CF code, there is no error but the code is not executed, just seen as though a text file.

So, it's best for me to close this, award you the points for the great effort, which may be close to being correct. But I have a feeling we'll never know until the main problem is found and corrected.

If and when the problem is found, I'll try to return here to post it.


I found the answer elsewhere. This works if you place it into the root web.config file.

<rewrite>
  <rules>
<rule name="Map htm to cfm" stopProcessing="true">  
  <match url="(.*)\.htm$" />  
  <action type="Redirect" redirectType="Permanent" url="{R:1}.cfm" />  
</rule>
  </rules>
</rewrite>

As previously mentioned, add the servlet mappings, edit the uriworkers.properties file, and then in the IIS config for the site in question, open the Handler Mappings configuration and EDIT the entry for cfmHandler. In the form, change "*.cfm" to "*.cfm,*.htm". Save. Restart IIS. Done.