Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Date: Fri, 8 Sep 2000 08:37:03 +0100 (BST)
From: James Sutherland <jas88@cam.ac.uk>
To: new-httpd@apache.org
Subject: RE: Logging aborted connections in the access log
In-Reply-To: <000401c01939$8d5804c0$92c0b0d0@roweclan.net>
Message-ID: <Pine.LNX.4.10.10009080831270.2352-100000@dax.joh.cam.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 7 Sep 2000, William A. Rowe, Jr. wrote:

> > From: Manoj Kasichainula [mailto:manoj@io.com]
> > Sent: Thursday, September 07, 2000 8:50 PM
> > 
> > On Thu, Sep 07, 2000 at 11:36:18AM -0400, Rodent of Unusual 
> > Size wrote:
> > > I like this option best, but "X"/"-" is awfully cryptic.  I'd
> > > prefer something meaningful (and greppable) like "successful"/
> > > "aborted"/"partial" (for an abort after some content had been
> > > sent).  I think this also has the most flexibility for expansion.
> > 
> > I prefer to not use words, simply because it's one less thing for
> > non-English speakers to want translated.
>  
> Good argument for symbology, or perhaps status 'numbered' conditions.
> 
> One extra thought... would it be useful to log more than one status
> here, now that we are 'inventing' a new concept?  I'm thinking about:
> 
> Completed - Kept Alive
> Completed - Socket Closed
> Aborted
> 
> Anything significant that I'm missing?  Excuse a -very- ignorant Q.
> Can we abort and still keep-alive?  

Not under HTTP, AFAICS, but we may well be able to in future - later HTTP
revisions, other protocols (FTP can, for example). Keep the option open if
possible, IMO.

How about something akin to HTTP status codes?

2xx = transfer completed
3xx = link error (e.g. socket closed)
4xx = user-commanded abort (e.g. FTP's ABOR command)
5xx = server error (out of memory, signalled)


James.