When a Microsoft ASP.NET-connected application receives a POST request, the data in the POST request is truncated to 49,152 bytes. This problem occurs if the following conditions are true:
- ASP.NET is registered as a wildcard script map.
- During the POST request, the HTML form that sends the POST request is accessed by an external process. For example, the HTML form is accessed by an HTTP module or by a global application event handler.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note
In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
To apply this hotfix, you must have the Microsoft .NET Framework 2.0 installed.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix replaces the hotfixes that are described in the following Microsoft Knowledge Base articles.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
FIX: Error message when you try to go to an ASP.NET page by using a URL that contains Unicode characters: "HTTP error 400 'bad request'"
FIX: You may experience an unexpected AppDomain restart in an ASP.NET Web application that is based on the .NET Framework 2.0
FIX: You receive an exception error message when you specify a Content-Length HTTP header that is larger than 2 GB in ASP.NET 2.0
FIX: You may receive an InvalidCastException error in an ASP.NET-connected Web application
FIX: You receive a ThreadAbortException exception in an ASP.NET Web application that is based in the .NET Framework 2.0 when the Async page directive property is set to true
MS06-056: Vulnerability in ASP.NET 2.0 could allow for information disclosure
FIX: Error message when you try to browse the root folder of a Web application that is built on the .NET Framework 2.0: "Object reference not set to an instance of an object"
FIX: Some characters in a text resource may not appear correctly when you try to embed the text resource in a Web application that is built on the .NET Framework 2.0
FIX: Error message when you try to run an ASP.NET 2.0 Web application that includes Web services: "The file <FilePath> does not exist"
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone
tab in the Date and Time
item in Control Panel.
Collapse this tableExpand this table
|File name||File version||File size||Date||Time||Platform|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates