IIS and HTTP API
From: Kornél Pál (anonymous_at_discussions.microsoft.com)
Date: 06/16/04
- Next message: Mike Schwarz: "virtual webs down with acccess"
- Previous message: Jeff Dillon: "Re: IIS 6.0 - logging everything!"
- Next in thread: David Wang [Msft]: "Re: IIS and HTTP API"
- Reply: David Wang [Msft]: "Re: IIS and HTTP API"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 16 Jun 2004 22:56:25 +0200
Hi,
I've found these articles:
http://support.microsoft.com/default.aspx?scid=kb;en-us;q311852
http://support.microsoft.com/default.aspx?scid=kb;en-us;q327611
First of all I've got a question. READ_RAW_DATA can be used to modify the
request body not only the headers. Why is it gone? If you don't want to
modify its behavior you should add a new notification type (input and output
as well) only for modifying the entity body.
But my main question is that this article says that IIS 6 operates quite
different in IIS 5 mode.
I section "SSL in IIS 6.0" I've read that in IIS 5 mode IIS 6 hosts SSL and
filters can use SF_NOTIFY_READ_RAW_DATA. This can mean one of the two tings:
1. IIS 6 is not using HTTP API at all.
In this case a lot of HTTP API based things can be broken, including HTTP
API based Windows system services and SQL Server Yukon's web services. If
it's the truth is a very strange thing.
2. IIS 6 is using undocumented HTTP API calls that make it possible to
process the raw data.
In this case you should document these APIs as they could be used by others.
httpapi.dll exports some undocumented functions (without header
declarations) that are used only by IIS. But as HTTP API is an operating
system service and not part of IIS I think you should document all the
functionality of HTTP API.
Sincerely,
Kornél
- Next message: Mike Schwarz: "virtual webs down with acccess"
- Previous message: Jeff Dillon: "Re: IIS 6.0 - logging everything!"
- Next in thread: David Wang [Msft]: "Re: IIS and HTTP API"
- Reply: David Wang [Msft]: "Re: IIS and HTTP API"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|