IIS 7 and Above
ISAPI and IIS 10 Logging Issues
Last post Sep 19, 2017 02:29 PM by Rovastar
Sep 05, 2017 08:28 PM|Miket03|LINK
When using the ISAPI Handler Mapping in IIS 10 on Windows 2016, the IIS logs are not identifying the URI Stem (cs-uri-stem) and URI Query (cs-uri-query) as expected. For EVERY request that the handler processes (e.g. default.cfm), the cs-uri-stem records
an entry as "/jakarta/isapi_redirect.dll" and the cs-uri-query is always empty.
On Window 2012 R2, IIS is not behaving this way.
Any help would be greatly appreciated!
Sep 06, 2017 08:06 AM|Yuk Ding|LINK
The IIS logging service responsible for the logging and it should record the string after question mark in cs-uri-query.
Sep 06, 2017 08:03 PM|Miket03|LINK
Here is a log Excerpt:
#Software: Microsoft Internet Information Services 10.0
#Date: 2017-07-02 00:00:00
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs-version cs(User-Agent) cs(Referer) cs-host sc-status sc-substatus sc-win32-status sc-bytes cs-bytes time-taken
2017-07-02 00:00:00 XX.X.X.XX GET /jakarta/isapi_redirect.dll - 443 - XX.X.X.XX HTTP/1.1
As you can see in the log, the columns are correct but the actual cs-uri-stem and cs-uri-query are not logged properly. It is only listing the ISAPI module that is called and not the page that was requested.
I read about this happening with "IIS Advanced Logging" feature here: https://forums.iis.net/p/1168716/2134036.aspx?Re+IIS+Advanced+Logging+issues+with+Tomcat+and+web+application
Do you know if IIS 10 incorporated specific changes in the logging of requests? Perhaps any updates as to how it handles ISAPI filters in general? It "feels" like IIS 10 incorporated the Advanced Logging features directly into the platform along with this
Sep 19, 2017 12:35 PM|Miket03|LINK
Did you see my previous post? Any movement with this topic? Still an outstanding issue on my end.
Sep 19, 2017 02:29 PM|Rovastar|LINK