Microsoft KB Archive/944836

= Information about the UrlScan 2.5 features that are included in IIS 7.0 =

Article ID: 944836

Article Last Modified on 11/21/2007

-

APPLIES TO


 * Microsoft Internet Information Services 7.0

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows XP and Windows Vista



INTRODUCTION
UrlScan 2.5 is an Internet Server API (ISAPI) filter that was developed to help administrators secure Web sites that are hosted on Internet Information Services (IIS) 5.0. Because improving security was a top priority, the features in UrlScan 2.5 were built into IIS 6.0. Improved security was also a priority in IIS 7.0. Therefore, the features of UrlScan 2.5 are also included in IIS 7.0.

This article contains descriptions of the UrlScan 2.5 features that are implemented in IIS 7.0. This article also contains a table that maps the features in UrlScan 2.5 to the settings in the Http.sys driver and to the settings in the Request Filtering feature in IIS 7.0.



MORE INFORMATION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

UrlScan 2.5 features that are implemented in IIS 7.0
The following table contains the names and descriptions of the UrlScan 2.5 features that are implemented in IIS 7.0.

Implementation of UrlScan 2.5 features in IIS 7.0
The following table maps the features in UrlScan 2.5 to the settings in the Http.sys driver and to the settings in the Request Filtering feature in IIS 7.0.

Notes
 * If a feature is marked &quot;Not applicable,&quot; IIS 7.0 implements the feature automatically, and no configuration is required.
 * IIS 7.0 configuration files must follow XML standards. Therefore, be careful when you use special characters in an XML file.


 * This value can be changed by modifying the following registry subkey:
 * HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters\EnableNonUTF8


 * The values can be changed by modifying AllowRestrictedChars, MaxFieldLength, UrlSegmentMaxLength, and UrlSegmentMaxCount in the registry under the following registry subkeys:

