On 01.09.2017 22:21, Thomas, Michael wrote:
> All,
> 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. .cfm), the 
> cs-uri-stem records an entry as "/jakarta/isapi_redirect.dll" and the 
> cs-uri-query is always empty.
> Environment Details:
> *         IIS 10 (Windows 2016)
> *         Tomcat
> *         Java 1.8.0_131
> *         ISAPI Connector 1.2.41
> *         ColdFusion 2016
> For comparison, we have a similar setup on another box (IIS 8.5 Windows 
> Server 2012 R2) and the logs are recording as expected.
> Any assistance would be great!

On 01.09.2017 22:37, Warnier, Andre wrote
>If I understand this correctly, the difference between your two setups above 
>is at the Windows/IIS level, not at the tomcat/ISAPI-redirector level.
>This may be naive, but isn't this a question then for the Windows/IIS people ?

Andre, you're right.  Perhaps this is a good question for the Windows folks.  I 
guess I was hoping that someone in this community has seen this issue before 
and had a recommended solution.

It is really challenging to not know what traffic your IIS Web Server is 
actually seeing.  There are of course other avenues (e.g. firewall logs, siem 
logs, etc) but the IIS logs are native to the boxes themselves and much easier 
to analyze.  I was curious if the ISAPI Connector returned a specific URL back 
to IIS and it could be tweaked.  Not sure if IIS is expecting a response in a 
certain format, etc.

Is there documentation that I can look at for what the ISAPI module should 
return to IIS?  Anyone have any insight into that pipeline?




The preceding message (including attachments) is covered by the Electronic 
Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only for 
the person or entity to which it is addressed, and may contain information that 
is confidential, protected by attorney-client or other privilege, or otherwise 
protected from disclosure by law. If you are not the intended recipient, you 
are hereby notified that any retention, dissemination, distribution, or copying 
of this communication is strictly prohibited. Please reply to the sender that 
you have received the message in error and destroy the original message and all 

To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to