Important This article contains information about how to modify the registry. Make sure to 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:
Consider the following scenario. You run a Microsoft ASP.NET application on a Microsoft Windows Server 2003-based computer. The Microsoft .NET Framework is installed on the computer. A client tries to open the Web site for the first time. In this scenario, the client may receive an error message that is similar to the following:
HTTP 400 – Bad Request
This problem occurs when the cookieless attribute of the sessionState element in the configuration file is set to true.
This problem occurs because the request was sent to the Windows Server 2003-based computer through a proxy. The proxy may modify the header value for the URL from a relative value to a fully qualified value.
Build a release version of the project, and then copy the generated DLL to the Drive:\Windows\System32\Inetsrv folder
Install the new filter
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 your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To install the new ISAPI filter, follow these steps:
You must update the registry key that specifies where filters are located. To do this, follow these steps:
Click Start, click Run, type regedit, and then click OK.