FIX: You receive an "OverflowException" error message when you specify a Content-Length HTTP header that is larger than 2 GB in the .NET Framework 1.1

In the Microsoft .NET Framework 1.1, when you specify a Content-Length HTTP header that is larger that 2 GB, you receive the following exception error message:

This problem occurs when Microsoft ASP.NET tries to parse the Content-Length HTTP header value as an Int32 data type. Therefore, if the value of the header is more than the maximum value of an Int32 data type, an overflow exception occurs. The maximum value of an Int32 data type is 2,147,483,647.

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product 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.

Prerequisites

The .NET Framework 1.1 Service Pack 1 (SP1)

Restart requirement

You must restart the computer after you apply this software update.

Hotfix replacement information

This hotfix does not replace any other software updates.

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 tool in Control Panel.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Steps to reproduce the problem

1. Put a zipped file that is larger than 2.5 GB on a Web server that is running Microsoft Windows Server 2003.
2. Install and configure a custom handler that includes one of the following methods to download a file:

   response.AddHeader("Content-Length", new FileInfo(fileName).Length.ToString()); 
   ' Specifies that the response is a stream that cannot be read by the
   ' client and must be downloaded.
   
   response.TransmitFile( fileName );
   ' The TransmitFile method enables sending output directly from a file to the ISAPI extension 
   ' and then back to the client without passing a huge string through the ISAPI extension. 
   ' The TransmitFile method uses a pointer to a file on disk, and it reads and transmits the file directly. 

3. Using a Web browser, open the 2.5 GB zipped file. You receive the error message that is mentioned in the "Symptoms" section .

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about how to create, how to deploy, and how to configure the handler, click the following article number to view the article in the Microsoft Knowledge Base: