Custom filters that add headers may generate an "out-of-memory" error or a "not enough storage" error (819876)



The information in this article applies to:

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Professional
  • Microsoft Windows 2000 Advanced Server

SYMPTOMS

When you create a Web application filter that adds headers to a request, the filter may generate an "out-of-memory" error or a "not enough storage" error. This problem may occur even though the header size is very small. This problem may also occur when you use the Internet Information Services (IIS) 5.0 Secure Sockets Layer (SSL) filter.

CAUSE

This problem occurs because IIS 5.0 incorrectly counts the entity data as part of the header data. This prevents the AddHeader function and SetHeader function from working correctly, and that causes filters that add headers to fail with "out-of-memory" or "not enough storage" errors.

This problem occurs with the SSL filter because when the filter decrypts a message, it must use the ReadNext function to fill the buffer with sufficient data to form a complete SSL message before the decryption can succeed. Some browser client programs, including Microsoft Internet Explorer, sometimes encrypt both the headers and the body of a POST message or PUT message at the same time. This requires that the SSL filter must buffer the whole request before it can decrypt the message.

RESOLUTION

Hotfix Information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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

Windows 2000 Service Pack 3 (SP3) or later is required to install this hotfix.

Restart Requirement

You must restart your computer after you apply this hotfix.

Hotfix Replacement Information

This hotfix does not replace any other hotfixes.

File Information

The English version of this hotfix has the file attributes (or later) 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
------------------------------------------------------------
23-Jun-2003    10:13  5.0.2195.6672   339,728   Asp.dll
23-Jun-2003    10:13  5.0.2195.6620   299,792   Fscfg.dll
23-Jun-2003    10:13  5.0.2195.6620     8,464   Ftpctrs2.dll 
23-Jun-2003    10:13  5.0.2195.6620     6,416   Ftpmib.dll 
23-Jun-2003    10:13  5.0.2195.6620     9,488   Httpmib.dll 
23-Jun-2003    10:13  5.0.2195.6758    13,584   Infoadmn.dll 
23-Jun-2003    10:13  5.0.2195.6758   248,080   Infocomm.dll 
23-Jun-2003    10:13  5.0.2195.6758    62,736   Isatq.dll 
23-Jun-2003    10:13  5.0.2195.6620     7,440   W3ctrs.dll 
23-Jun-2003    10:13  5.0.2195.6755   349,968   W3svc.dll

STATUS

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

MORE INFORMATION

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

816915 New file naming schema for Microsoft Windows software update packages


Modification Type:MinorLast Reviewed:10/28/2005
Keywords:kbHotfixServer kbQFE kbBug kbfix kbQFE kbWin2000preSP5fix KB819876 kbAudITPRO