My goal seems simple.
I want IIS 7.5 to handle **ALL** 404 File Not Found requests, whether to static or dynamic (ColdFusion 9) content, and direct users to its custom 404 HTML page.
I believe that the IIS settings I need are existingReponse=Replace, errorMode=Custom, and a file path specified for the 404. That's what I've done.
With a CF10 install, it works. With CF9, **for some reason both the static IIS 404 response AND the ColdFusion 404 response are sent to the client and displayed**. Very weird.
I've tried all manner of alternate configurations, and there seems to be some problem with each approach.
Any ideas why IIS would fail to replace Coldfusion's 404 message? Is ColdFusion failing to communicate to IIS (via the appropriate header) that it's sending a 404? Is IIS being obstinate? Why would it be different with CF10 and CF9?
--------------------------
ColdFusion 9, via CFAdmin
--------------------------
Global Settings
- Missing Template Handler = [no path specified]
--------------------------
IIS 7, via IIS Manager
--------------------------
Configuration Editor -> system.webServer/httpErrors
- allowAbsolutePathWhenDelegated = false
- defualtPath = [no path specified]
- defaultResponseMode = File
- errorMode = Custom
- existingResponse = Replace
Configuration Editor -> system.webServer/httpErrors -> Edit Collection
- 404 Error
path = [DriveLetter]:\inetpub\wwwroot\CAES\global\errorHandling\404.html
prefixLanguageFilePath = [none specified]
respnseMode = File
statusCode = 404
subStatusCode = -1
- 403 Error
path = [DriveLetter]:\inetpub\wwwroot\CAES\global\errorHandling\403.html
prefixLanguageFilePath = [none specified]
respnseMode = File
statusCode = 404
subStatusCode = -1