You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "Roy T. Fielding" <fi...@avron.ICS.UCI.EDU> on 1995/05/06 15:28:06 UTC
Re: hmmm...
> This might be bad form to complain about this functionality this late in
> the game, but conceptually I have a hard time justifying the
> two-web-log-hits effect of error response redirects. I.e., when I access
> a protected area under a bogus username/password:
>
> fully - asdfsaf [19/Apr/1995:01:03:05 -0700] "GET /Login/ HTTP/1.0" 401 -
> fully - asdfsaf [19/Apr/1995:01:03:05 -0700] "GET /401.html" 200 703
>
> The problem is that the second one, when not in the context of the first,
> looks like a valid user "asdfsaf" accessed a page under authentication.
> I'd have to tell my scripts "no, no, toss out all accesses to 401.html
> before doing any user-based analysis".
>
> What do people think?
I think this is a bug. The common logfile format was intended to
log user requests, not server actions. Saying that the server received
a request "GET /401.html" is lying.
......Roy
584 messages down, 1109 to go (geez, if I could just get people
to stop work for a while...)
Re: hmmm...
Posted by Brian Behlendorf <br...@organic.com>.
On Sat, 6 May 1995, Roy T. Fielding wrote:
> > fully - asdfsaf [19/Apr/1995:01:03:05 -0700] "GET /Login/ HTTP/1.0" 401 -
> > fully - asdfsaf [19/Apr/1995:01:03:05 -0700] "GET /401.html" 200 703
>
> I think this is a bug. The common logfile format was intended to
> log user requests, not server actions. Saying that the server received
> a request "GET /401.html" is lying.
Right. I think we left the consensus at something like this:
The CLF is too restrictive, as the object requested may be significantly
different than the one received, so we need a way to specify both in the
logfile. This is true for many actions, multiviews for example - just
looking at logfiles won't tell me how many mother.html's versus
mother.html3's were serviced. However, it was deemed well and good to
still log server internal redirects while waiting for CLF2, so *for*now*
(and it's well documented, supposedly) that redirect is logged as a
separate, but concurrent, access. Maybe our next order of business
should be working on CLF2 (and CGI 1.2, and... :)
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com brian@hyperreal.com http://www.[hyperreal,organic].com/