Re: Configurable log proposal
luotonen@ptsun00.cern.ch (Ari Luotonen)
From: luotonen@ptsun00.cern.ch (Ari Luotonen)
Date: Wed, 2 Feb 94 10:53:19 +0100
Message-id: <9402020953.AA01425@ptsun03.cern.ch>
To: www-talk@www0.cern.ch
Subject: Re: Configurable log proposal
Content-Length: 1669
This was meant for the list.
----- Begin Included Message -----
From koblas@netcom.com Wed Feb 2 09:17:00 1994
From: koblas@netcom.com (David Koblas)
Subject: Re: Configurable log proposal
To: luotonen@ptsun00.cern.ch (Ari Luotonen)
Date: Wed, 2 Feb 1994 00:09:30 -0800 (PST)
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Content-Length: 1205
>...and what else? I would be happy to implement this. Maybe the %letters
>could be selected in a better way and not respect the ones strftime()
>uses.
%letters is 80's style programming, this is the nineties. After all most of
us probably read enough cryptic files every day. It would be nice if
it was more like:
HTTP:
TIME time
BYTES bytes transmitted
FILE requested FILE
URL requested URL
HOSTNAME client host address
EMAIL user email address
AUTH_USER authenticated username
REMOTE_USER remote ident
METHOD method
HTTP_VERSION protocol version
Where a formatting like would be something like (eg httpd 1.1):
$HOST [$TIME] $METHOD $FILE $HTTP_VERSION
Standard shell formatting rules apply. The only "unanswered" problem is
how to handle $TIME formatting since are two ways you could do it:
$TIME{"%a %b %d %T %Y"}
or
$TIME_WK $TIME_MON $TIME_TIME $TIME_YEAR
[general rule for the above]
TIME_WK abbreviated weekday
TIME_WEEK weekday
Food for thought,
--koblas@netcom.com
----- End Included Message -----