CF2023 CFM Files Not Served

[AlexCraig]

Am developing a site which is up & running with CF2023.

It serves html pages just fine. However, cfm files produce the following error.  Note: I do have an active mapping to the folder containg the code for the site.

I would be very grateful for any suggestions.  Thanks in advance.

HTTP Error 404.3 - Not Found

The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.

Most likely causes:

• It is possible that a handler mapping is missing. By default, the static file handler processes all content.
• The feature you are trying to use may not be installed.
• The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.)
• If ASP.NET is not installed.

[Charlie Arehart · Accepted solution]

There's no need of a mapping to the folder with your code. You're using IIS, right? Have you run the cf2023 web server configuration tool? Use that to connect iis (all sites or any one) to cf. That will add the *handler mapping* for cfm, cfc, and other cf-related extensions. It will also add an isapi filter as well as a needed jakarta virtual directory, both pointing to a folder containing an isapi_redirect.dll, both of which will be created in a folder within cf's config/wsconfig directory that the wsconfig tool will create. See the cf docs for more on this, if needed. 

[AlexCraig]

Much appreciate the prompt reply.  Yes, am running IIS.  Will run the web server configuration tool & report back.

[AlexCraig]

I had to add some components to IIS that were not included when I initially configured it.  But after that the web config tool ran without issue and cfm files are now being processed properly.

Thanks a bunch Charlie!

PS  Actually, this is part of project invoving upgrading a site with thousands of lines of code running under CF 4.50 that has been up since the turn of the century on a Windows 2000 server.  I'm finally at a point where it is time for an SSL certificate.  Frankely, otherwise, I wouldn't invest the time & effort as the old system runs flawlessly.

My only real concern is that CF2023 no longer includes the Verity Collections.  I love the robust searches we're able to do with Verity and modifying the code to run Solr will be a chore.  I'm guessing that, if feasible using Verity as an external search engine, if feasible, would cost a fortune!

[Charlie Arehart]

Good to hear and glad to have helped. And welcome your app to the 21st century. 🙂

As for adding SSL, since it's new for that app, don't spend a lot of money on it. You can have certs for free now. Have you heard of the Let's Encrypt project? And have you tried the nifty tool to make that easy on Windows, called CertifyTheWeb, which can be free for prod?

Finally, about verity vs solr, yep. That was a change in cf9. Most found that migration from verity to solr went fairly smooth. But yep, adding Verity in on your own would be expensive. Probably cheaper to spend the time on that migration. 

[AlexCraig]

Thanks again Charlie.

Also, much appreciate the SSL tips.  We have a much smaller companion site running on a Windows 2016 server which is SSL certified.  Cost was $85, but it required some DNS entries.  Since we serve our own DNS it wasn't really an issue.  But "free" is better than $85/annum.   😉

Am running into some session handling issues with 2023 that will probably be tougher to rectifiy than this problem.  Will tackle them next.  Just a thrill a minute!