I have IIS on my web servers log to a central server. To do this I followed the following links: Configuring IIS to Log Data on a Remote Share: http://technet.microsoft.com/en-us/library/cc757377.aspx Setting Up a Null Session for Cross-Domain Logging: http://technet.microsoft.com/en-us/library/cc728059...

I'm using UrlScan 3.0 on IIS 6.0 (IIS 7.0 is not an option). I need to block all requests for URLs which contain "NR" as a path segment: http://localhost/ NR /.... Here's my UrlScan.ini file (most settings are the defaults, changes are in italics, things I think are significant are...

In our URLScan logs we get the following quite a bit - - - - - - - - - - - - - - - - - - - - - - - - #Software: Microsoft UrlScan 3.0 #Version: 1.0 #Date: 2008-09-04 01:01:20 - - - - - - - - - - - - - - - - - - - - - - - - Does anyone know if this means that UrlScan is recycling and we have a period...

Doing some testing, currently, and running into some issues with this. We've got a couple cases where things like 'cast' or 'open' are appropriate for our webpages. I've setup an AlwaysAllowedQueryStrings section: [AlwaysAllowedQueryStrings] branch=Openshaw branch=Newcastle+upon...

Hi Zhao, Thank you for your reply. I now understand how [AlwaysAllowedUrls] works and where the query string check is still performed on the allowed Urls. To clarify, here is what I would like to achieve. For instance, I would like the following 'url+query string' to be valid: http://www.domain...

I would like to allow a search page to accept all text in the query string. To do this I added the result page to the [AlwaysAllowedUrls]. One thing that is ambiguous from the documentation is if the [AlwaysAllowedUrls] settings also bypasses the custom rules and if the pages listed in [AlwaysAllowedUrls...