Non-Parsed Headers Stripped From CGI Applications That Have nph- Prefix in Name (280341)


The information in this article applies to:

  • Microsoft Internet Information Server 4.0
This article was previously published under Q280341

SYMPTOMS

If a CGI application that is designed to return non-parsed headers has an "nph-" prefix in the application name, the headers are stripped and not sent to client. This problem occurs after you apply Microsoft Windows NT Service Pack 6 (SP6), or later, hot fixes for Internet Information Server (IIS).

CAUSE

This is a regression to another fix that was created to handle headers when you use CGI output in an .stm or .shtml page. By using the #EXEC CGI directive in an .stm page, you can execute a CGI application and have the contents merged with the rest of the .stm page. To facilitate this correctly, a fix was created that strips the headers from CGI applications. This corrected the SSINC scenario, but caused stand-alone "nph-" CGI applications not to send any headers to the client.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

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 fix should have the following file attributes or later:
   Date        Time          Version     Size        File name     Platform
   ------------------------------------------------------------------------

   1/10/2001   1:20:53 P.M.  4.2.755.1   214,544 KB  Adsiis.dll     x86
   1/10/2001   1:21:13 P.M.  4.2.755.1   330,672 KB  Asp.dll        x86
   1/10/2001   1:20:18 P.M.  4.2.755.1   55,904 KB   Httpodbc.dll   x86
   1/10/2001   1:20:54 P.M.  4.2.755.1   98,912 KB   Iischema.dll   x86
   1/10/2001   1:19:30 P.M.  4.2.755.1   185,792 KB  Infocomm.dll   x86
   1/10/2001   1:20:25 P.M.  4.2.755.1   38,256 KB   Ssinc.dll      x86
   1/10/2001   1:20:33 P.M.  4.2.755.1   25,360 KB   Sspifilt.dll   x86
   1/10/2001   1:20:12 P.M.  4.2.755.1   229,008 KB  W3svc.dll      x86

   1/10/2001   1:23:23 P.M.  4.2.755.1   307,984 KB  Adsiis.dll     alpha
   1/10/2001   1:23:45 P.M.  4.2.755.1   553,232 KB  Asp.dll        alpha
   1/10/2001   1:22:51 P.M.  4.2.755.1   89,872 KB   Httpodbc.dll   alpha
   1/10/2001   1:23:27 P.M.  4.2.755.1   107,280 KB  Iischema.dll   alpha
   1/10/2001   1:12:03 P.M.  4.2.755.1   305,424 KB  Infocomm.dll   alpha
   1/10/2001   1:22:57 P.M.  4.2.755.1   60,688 KB   Ssinc.dll      alpha
   1/10/2001   1:23:04 P.M.  4.2.755.1   39,696 KB   Sspifilt.dll   alpha
   1/10/2001   1:22:45 P.M.  4.2.755.1   384,272 KB  W3svc.dll      alpha

STATUS

Microsoft has confirmed that this is a problem in Internet Information Server 4.0.
Modification Type:MinorLast Reviewed:9/23/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix KB280341
©2004 Microsoft Corporation. All rights reserved.