Select the product you need help with

FIX: "HTTP 400 - Bad request" error message in the .NET Framework 1.1

Article ID: 826437 - View products that this article applies to.

SYMPTOMS

When you run the Microsoft .NET Framework 1.1, and then you visit a URL that contains a second colon (":"), you receive the following error message:

1.1 - HTTP 400 - Bad Request

For example, the following URL generates this error message:

http://server/folder/page.aspx/http://www.wingtiptoys.com

Note You may also receive this error message if the URL contains the following characters:

* % &

Back to the top | Give Feedback

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756

(http://support.microsoft.com/kb/322756/ )

How to back up and restore the registry in Windows

To browse URLs that contain the characters that are mentioned in the "Symptoms" section, obtain the latest service pack for the Microsoft .NET Framework 1.1. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

885055

(http://support.microsoft.com/kb/885055/ )

How to obtain Microsoft .NET Framework 1.1 Service Pack 1

Registry information

Important If you enable this fix, you increase the attack surface of the application. You should not enable this fix unless the application requires it.

After you install the service pack, set the following registry key to enable the fix:

DWORD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET VerificationCompatibility = 1

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in the .NET Framework 1.1 Service Pack 1.

Back to the top | Give Feedback