FIX: A socket may close unexpectedly and performance may decrease when you send an empty HTTP request to IIS 6.0 in the .NET Framework 1.1 (867487)



The information in this article applies to:

  • Microsoft .NET Framework 1.1

SYMPTOMS

You work with an application that uses Microsoft Internet Information Services (IIS) 6.0 and an HTTP request for content is made. If IIS is configured to reply with code 304 - Not modified and if the request for content is empty or "0", the socket that contains the request may close unexpectedly. When new HTTP requests are made on the application, IIS must open new sockets instead of reusing the now-closed sockets. This scenario may cause the application that uses IIS to have a significant decrease in performance.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for the Microsoft .NET Framework 1.1 . For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

885055 How to obtain Microsoft .NET Framework 1.1 Service Pack 1

Hotfix information

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 1.1 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.

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.
  Date         Time   Version       Size       File name
  -----------------------------------------------------------------------
  15-May-2003  18:49                   34,150  InstallSqlState.sql  
  15-May-2003  18:49                   33,522  InstallPersistSqlState.sql 
  02-Jul-2003  16:54                   14,472  WebUIValidation.js  
  02-Jul-2003  16:58  1.1.4322.919     32,768  aspnet_wp.exe 
  02-Jul-2003  16:58  1.1.4322.919     20,480  aspnet_regiis.exe  
  02-Jul-2003  16:58  1.1.4322.919    253,952  aspnet_isapi.dll 
  03-Jul-2003  07:19  1.1.4322.919  1,249,280  System.Web.dll 
  03-Jul-2003  07:20  1.1.4322.919  1,216,512  System.dll 

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.

MORE INFORMATION

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

824684 Description of the standard terminology that is used to describe Microsoft software updates


Modification Type:MinorLast Reviewed:10/7/2005
Keywords:kbQFE kbfix kbbug KB867487 kbAudDeveloper kbAudITPRO