--
On 17/11/17 15:47, jumiller wrote:
> I finally managed to figure out what the issue is/was. The
> c:\windows\system32\inetsrv\config\applicationHost.config file has a
> definition for IsapiFilter in the overrideMode="Allow">
-
On 06/10/17 22:42, Mark Thomas wrote:
> On 06/10/17 16:27, Mark Thomas wrote:
>>> On 10.05.2017 8:54, Thomas, Michael wrote:
>>>
>>> Unfortunately I am not getting much traction with Microsoft. Fro
for IIS 8) it says "are replaced".
All of this without any guarantee though, I am not an MS expert in any way.
----------
On 05.10.2017 17:09, Thomas, Michael wrote:
Just want to drop a few questions:
Are folks who develop
--
On 06.09.2017 22:07, Thomas, Michael wrote:
>
> --
>> On 01.09.2017 22:21, Thomas, Michael wrote:
>>> All,
>>>
>>> When
--
> 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)
--
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)
&
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
All,
I am having an issue with IIS Logs on Windows 2016. Specifically, the
cs-uri-stem and cs-uri-query columns are not recording requests properly. For
EVERY request that is handled by the connector, the cs-uri-stem records an
entry as "/jakarta/isapi_redirect.dll" and the cs-uri-query is
