tracker issue : CF-4170897

select a category, or use search below
(searches all categories and all time range)
Title:

Coldfusion does not render HTML pages with proper Script Mapping in IIS

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): K VN / K VN (K VN)

Created: 07/06/2016

Components: Documentation

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: CF2016_Update1 / docs

Priority/Frequency: Normal / Few users will encounter

Locale/System: English / Windows 10 64 bit

Vote Count: 0

Problem Description: Setting IIS to render .html pages as ColdFusion returns a blank page. Previous versions of ColdFusion would allow for proper execution.

Steps to Reproduce: https://helpx.adobe.com/coldfusion/kb/render-html-pages-using-coldfusion.html

Actual Result: Blank source

Expected Result: Rendered HTML and ColdFusion code

Any Workarounds:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4170897

External Customer Info:
External Company:  
External Customer Name: K VN
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

Thanks for pointing this out. In addition to the configuration edits to web.xml and IIS, you would also need to edit {CF-INSTALL_DIR}\config\wsconfig\{MAGIC-NUMBER}\uriworkermap.properties to include *.html. The docs are essentially out of date in the below areas. We will get this updated. But on the other hand, the method actually adds additional overhead on ColdFusion servers. An ideal deployment would off-load static files to the webserver. Do you see yourself using this configuration on production servers?
Comment by Immanuel N.
2215 | July 08, 2016 05:47:54 AM GMT
I appreciate the response. I previously attempted your proposed solution and a simple test page returns an Apache Tomcat HTTP Status 404 error. I don't foresee utilizing this configuration heavily. However, the ability to do so can prove to be valuable when dealing with legacy websites.
Comment by External U.
2216 | July 08, 2016 08:14:56 AM GMT