Hi!
Microsoft describes http.sys as the kernel mode cache of IIS 6, however it's
kernel mode HTTP listener with cache for any application.
Using http.sys Apache HTTPD could be used with IIS 6 on Windows sharing the
same port and IP address. I think this is a good thing if you want to host
more we
From: "Kornél Pál"
>
> Microsoft describes http.sys as the
> kernel mode cache of IIS 6, however it's
> kernel mode HTTP listener with cache for
> any application.
>
The HTTP application programming interface
(API) enables applications to communicate
over HTTP without using Microsoft Internet
> To successfully allow applications to
> use the same port on different IP
> addresses, you must use a new utility,
> Httpcfg.exe.
I don't agree with MUST as it uses HTTP API and it's source code is
available as well.
See http://msdn.microsoft.com/library/en-us/http/http/httpcfg_exe.asp
> So I g
Thanks for the interesting references and citations.
Apache HTTP server works at a lower level, below the layer exposed
by this http.dll API. To actually use this interface would require a few
things;
1a) Either support the http channel with the apr_socket_foo() API (this
is not a great opt
William A. Rowe, Jr. wrote:
Thanks for the interesting references and citations.
Apache HTTP server works at a lower level, below the layer exposed
by this http.dll API. To actually use this interface would require a few
things;
1a) Either support the http channel with the apr_socket_foo() API (th
From: "Kornél Pál"
> > To successfully allow applications to
> > use the same port on different IP
> > addresses, you must use a new utility,
> > Httpcfg.exe.
>
> I don't agree with MUST
I believe, in this "one" article (for 98
percent of the non coding admins) the
word "must" is correct for th
At 11:47 AM 6/21/2004, Bill Stoddard wrote:
>William A. Rowe, Jr. wrote:
>
>>Thanks for the interesting references and citations.
>>Apache HTTP server works at a lower level, below the layer exposed
>>by this http.dll API. To actually use this interface would require a few
>>things;
>>1a) Either s
William A. Rowe, Jr. wrote:
At 11:47 AM 6/21/2004, Bill Stoddard wrote:
William A. Rowe, Jr. wrote:
Thanks for the interesting references and citations.
Apache HTTP server works at a lower level, below the layer exposed
by this http.dll API. To actually use this interface would require a few
thin
From: "William A. Rowe, Jr."
> Thanks for the interesting references and citations.
Yes but for anyone with the equipment
to test this stuff, the real interesting stuff
is just beginning in the next few months
or years.
Being a retired old man without equipment,
(but still doing odd jobs) othe
At 01:16 PM 6/21/2004, Bill Stoddard wrote:
>William A. Rowe, Jr. wrote:
>>
>>Scratch my proposal 1a) - your solution 1c) is the obvious choice if the
>>user attempted to do this within apr...
>>But it's not practical, in this case because http.dll isn't just another low-level
>>interface, but a v
Replay to William A. Rowe, Jr.'s 1) - 2):
I think this should be implemented as new MPM as in other cases the data
prepocessed by HTTP API sould be used to construct lower level things (even
raw request bytes at some level) and this would kill the goals of HTTP API.
Only thing you have to do is t
> I believe, in this "one" article (for 98
> percent of the non coding admins) the
> word "must" is correct for the new way
> to control Windows ports.
>
> This article does not "mean" for "everyone"
> this is the only way.
>
> Always ask who is this article written for?
>
> Then add your own know
From: "Kornél Pál"
> > I believe, in this "one" article (for 98
> > percent of the non coding admins) the
> > word "must" is correct for the new way
> > to control Windows ports.
> >
> > This article does not "mean" for "everyone"
> > this is the only way.
> >
> > Always ask who is this article w
From: "Kornél Pál"
> Jeff White wrote:
> >HTTP.SYS is for quick static responses.
> >
> >They may be cached html files sent via
> >the Windows kernel. Not a real new big
> >business web server. But may be a server
> >for the one man shop and may be for security
> >of open ports, etc. :)
>
> I h
At 04:17 PM 6/21/2004, Kornél Pál wrote:
>[...]
>And I think filters that are processing raw data should be ignored for this
>MPM as they are not usefult in this situation and the raw data should be
>recreated from HTTP API structures to can be passed to filters and then
>reprocessed again. Other f
>>And I think filters that are processing raw data should be ignored for
this
>>MPM as they are not usefult in this situation and the raw data should be
>>recreated from HTTP API structures to can be passed to filters and then
>>reprocessed again. Other filters dealing with headers and entity body
> > >HTTP.SYS is for quick static responses.
> > >
> > >They may be cached html files sent via
> > >the Windows kernel. Not a real new big
> > >business web server. But may be a server
> > >for the one man shop and may be for security
> > >of open ports, etc. :)
> >
> > I have to say you are wrong
> I do not understand any of the above,
> please explain...
This means that this newsgroup is about development and is subjected mainly
to developers and not administrators.
Thus I think if we provide some information we have to provide it to be
subjected to developers and not administrators as we
From: "Kornél Pál"
> > I do not understand any of the above,
> > please explain...
>
> This means that this newsgroup is about
> development and is subjected mainly
> to developers and not administrators.
My post was for developers.
And I am well aware that many admins
read this list too.
But
From: "Kornél Pál"
> > > I have to say you are wrong.
> >
> > Okay I often am but where? :)
>
> I've quoted the lines in your are wrong in my opinion.:)
> Summarized:
> only static files,
I said:
"HTTP.SYS is for quick static responses"
The HTTP API provides developers with a
low-level in
> The HTTP API provides developers with a
> low-level interface to the server side of the
> HTTP functionality as defined in RFC 2616.
> The API allows the application to receive
> HTTP requests directed to URLs of interest
> to it, and send HTTP responses. For sending
> dynamic responses, however,
>ASP.NET is a better choice for a web application because it's easier to be
>used by a programer.:)
Religious discussions are off-topic on this list...
>However ASP.NET uses IIS 6 and IIS 6 uses HTTP API so
>nothing will be faster. But Apache HTTPD is a web server not a web
>application.
Yes bu
> >ASP.NET is a better choice for a web application because it's easier to
be
> >used by a programer.:)
> Religious discussions are off-topic on this list...
It wasn't only my opinion it was an aswer to a quotation or an
interpretation of it that said ASP.NET is better than HTTP API. It's true
for
Before one moves on to what I was
told was the real topic of this thread...
> "Kornél Pál"
> however this topic is about using
> HTTP API in Apache HTTPD.
First let's clear up some ideas. :)
Forgetting about logging for now.
> WRowe
> I thought the entire point was that it
It being the HTTP.S
>
> In .NET Framework (soon out):
>
> HttpListener class (uses HTTP.SYS)
> Defined as a simple web server
>
In below article, jump to:
Web Services Anywhere
There are some interesting scenarios
that require exposing a Web service
from an application that is not running
in IIS; for examp
25 matches
Mail list logo
