Title:
[ANeff] Doc ER for: document solution for IIS10 logs CF requests incorrectly if IsapiFilterModule after HttpLoggingModule
| View in TrackerStatus/Resolution/Reason: Closed/Fixed/Fixed
Reporter/Name(from Bugbase): Aaron Neff / ()
Created: 04/21/2018
Components: Documentation
Versions: 2018
Failure Type: Others
Found In Build/Fixed In Build: / NA
Priority/Frequency: Normal /
Locale/System: /
Vote Count: 0
Issue: In IIS10, IIS logs CF requests incorrectly in a specific scenario. The simple solution should be documented.
Steps to Reproduce:
1) In C:\Windows\System32\inetsrv\Config\applicationHost.config, in the '<location path="" overrideMode="Allow"><modules>' section, place IsapiFilterModule after HttpLoggingModule in the list.
2) Make a request for domain.com and see IIS logged cs-uri-stem as "/" (good)
3) Make a request for domain.com/index.cfm and see IIS logged cs-uri-stem as "/jakarta/isapi_redirect.dll" (bad)
Note: Other fields are also logged incorrectly. Just using cs-uri-stem as an example.
This issue affects clean installs of IIS10, since IsapiFilterModule comes after HttpLoggingModule by default in IIS10.
Suggestion: The "Prepare to install ColdFusion" doc should mention the following bullet, under "Installation considerations for Windows"
-----------
- In IIS10's C:\Windows\System32\inetsrv\Config\applicationHost.config, in the '<location path="" overrideMode="Allow"><modules>' section, IsapiFilterModule must be before HttpLoggingModule in the list. Otherwise, IIS may log CF requests incorrectly (ex: a request for domain.com/mypage.cfm may have cs-uri-stem logged as "/jakarta/isapi_redirect.dll" instead of "/mypage.cfm").
-----------
Related URL: https://helpx.adobe.com/coldfusion/installing/preparing-to-install-coldfusion.html
Related URL: https://forums.iis.net/post/2137409.aspx
Related thread: https://forums.adobeprerelease.com/coldfusionpr/discussion/225/iis-connector-logs-cs-uri-stem-as-jakarta-isapi-redirect-dllAttachments:
Comments: