Hey everyone,
I tried setting up IIS Failed Request Tracing for one and only one specific URI to debug a problem that persists with this URI. The problem about filtering it is that it's a HTTP 200 response that contains an error message from a 3rd party solution in SharePoint.
So I set up Tracing for the URI, say /mywebsite/3rdpartyapp/_vti_bin/client.svc/ProcessQuery. That's what I entered in the custom field in the first step of the Tracing wizard. I entered code 200 as the HTTP Response Code criterion.
Now I get many, many Trace logs for /_vti_bin/client.svc/ntlm/ProcessQuery. But this is something I didn't even want to aim my telescope at.
I understand that it's basically possible to use wildcards in the configuration, but I didn't use any. Also, entering something like 3rdpartyapp*ProcessQuery resulted in getting many ntlm/ProcessQuery logs.
Thus I guess that the URI filter criterion is not handled as I expect it to work.
Can anyone tell me how IIS handles this exactly? Is only the last part of the expression ("ProcessQuery") actually evaluated or something like that?
System: Windows SBS 2011 with IIS 7.5
Kind regards
Nico