httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy T. Fielding" <field...@avron.ICS.UCI.EDU>
Subject Re: non-forking wish list
Date Sun, 11 Jun 1995 21:59:30 GMT
rst said:

> Hmmm... pipe dream warning II:  one way to support this would be to
> support some form of a status request, perhaps along the lines of:
>    SERVER_STATUS peformance-stats Apache-internal/0.8.x
> or
>    SERVER_STATUS requests-in-process Apache-internal/0.8.x
> and have the graphical front-end, or whatever, periodically make these
> requests.  Naturally, you'd want some form of very strict, presumably
> IP-address-authenticated, access control on these...
> (Note the Apache-internal "protocol" specifier, which should hopefully
> distinguish these now and forever from any legitimate form of HTTP).

Why?  HTTP was designed to handle arbitrary methods -- the HTTP/1.0
just indicates the message format.

In this case, however, it doesn't make sense to use a different 
method, since all you are doing is a GET on a special resource.

    GET /APACHE/performance HTTP/1.0

and just apply access control to /APACHE.

Or, if you want to make it harder for normal browsers to get the results:

    GET apache:performance HTTP/1.0

You can also do a variety of amusing things, like extra path info
to restrict the stats domain

    GET /APACHE/requests/~fielding/home.html HTTP/1.0
    GET /APACHE/requests; HTTP/1.0
    GET /APACHE/requests/argus.html;dates=19940101-19941231 HTTP/1.0

You can even measure the probe effect   :)

    GET /APACHE/requests/APACHE/performance HTTP/1.0

and for those truly fascinated by probe effect stuff

    <IMG src="http://myserver/APACHE/request_graph/thispage">

The possiblilities are (unfortunately) endless.


View raw message