IIS Returns CF file rather than handing request to CF
Am running IIS on a Windows 2016 server and ran an install of Coldfusion 2018(now on update 5). It installed, I ran wsconfig to configure the single website on this server, but IIS doesn't appear to be handing the request off to CF. What I'm getting instead is a question on how to handle the test.cfm file.
In the IIS UI, I have a cfmhandler mapping going to the isapimodule, and an ISAPI filter entry pointing to the correct subfolder in the CF installation (..config\wsconfig\1\isapi_redirect.dll).
I've installed CF a number of times before including using the lockdown guide. Haven't seen this before though.
To be clear, if you configure the connector for "all sites", that puts those things there for all the sites there at that time, and at the server level for all sites to inherit.
But if you add a new site after that, iis only propagates the isapi filter and mappings into a new site. There's no provision in iis for new sites to inherit virtual directories. You need to add them yourself. Same with the cf_scripts vd.
Such a change takes effect immediately, no restart of iis or cf needed.
If it's not that, let us know and we can dig still further.