httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Sutherland <ja...@cam.ac.uk>
Subject RE: Logging aborted connections in the access log
Date Fri, 08 Sep 2000 19:18:36 GMT
On Fri, 8 Sep 2000, William A. Rowe, Jr. wrote:

> > From: James Sutherland [mailto:jas88@cam.ac.uk]
> > Sent: Friday, September 08, 2000 11:30 AM
> >
> > Hrmm... The usual server responses have a nice solution to 
> > this - "911 I hate you" or whatever. Both human and both
> > parsable. The trouble is, an explanation of what happened 
> > would be a bit too bulky to file, I think, certainly for some uses.
> 
> Ok... hot button issue :-)  Size alone, 2+ bytes, dictates 
> (code, 1+ digits, and space) that we aught to have a simple code
> system, allowing us to see if the request (and connection) were
> terminated (and how, if known.)

Agreed. How about a digit by digit breakdown, as for HTTP status codes?

> > How about supporting both numerical and human result codes, 
> > and keeping the two distinct? (i.e. you would get "911" 
> > and/or "I hate you", depending on config: readable if you 
> > want, fast and compact otherwise.)
> 
> Perfectly acceptable, I'd make this case sensistive (caps for any
> logged entry in 'textual' mode, lowercase for any logged 'status'.)
> 
> The point?  Let's translate -any- code (http status, etc...) for
> the log reader, if the administrator chooses :-)

Good idea. Do we want this done by the httpd on the fly, though?? This
sort of end-user handholding looks more like a job for a post-processor to
me.


James.


Mime
View raw message