The custom headers could be coming from a metabase setting.
In the IIS MMC, open the properties of the web site and select the HTTP
Headers tab, verify that your custom headers a not specified in the Custom
HTTP Headers section.
Lou Prete [MSFT]
This posting is provided “AS IS” with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.
--------------------
| From: "Tim Wallace" <reply.TakeThisOut@this_group.com>
| Subject: ISAPI
| Date: Mon, 3 May 2004 01:16:58 -0400
| Lines: 9
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <eAfUP2MMEHA.556.TakeThisOut@TK2MSFTNGP10.phx.gbl>
| Newsgroups: microsoft.public.inetserver.iis
| NNTP-Posting-Host: pcp01730859pcs.lpaxtn01.pa.comcast.net 68.83.110.23
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10
phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.inetserver.iis:305424
| X-Tomcat-NG: microsoft.public.inetserver.iis
|
| I wrote an ISAPI filter and installed it on my Web server. Basically, it
| adds headers to the response headers. Here's my problem: I removed it
from
| IIS and the custom headers are still included. I even rebooted the
machine,
| still there. I even changed the DLL extension and rebooted...still there.
| Does anyone know how I can remove these headers?
|
| Tim
|
|
|
>> Stay informed about: ISAPI