From new-httpd-return-7689-apmail-new-httpd-archive=apache.org@apache.org Thu Sep 07 14:00:47 2000 Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 71975 invoked by uid 500); 7 Sep 2000 14:00:45 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 71964 invoked from network); 7 Sep 2000 14:00:44 -0000 Message-ID: <00bc01c018d4$a9448fb0$e4421b09@raleigh.ibm.com> From: "Bill Stoddard" To: Subject: Logging aborted connections in the access log Date: Thu, 7 Sep 2000 10:05:21 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N It would be useful to note in the access log when a request has been aborted by the client. The condition is easy to detect in mod_log_config by checking r->connection->aborted. I've considered several ways to log the info, none of which are particularly appealing: 1. Introduce a new LogFormat formatting field, %c, which would spit out a suitable indicator. " X" if the connection was aborted, "-" otherwise. 2. Tweaking the behavious of the %s format field (%s displays the response status) thusly.. 200 ==> good response, 200x ==> Good response, but the client closed the connection before the response could be forwarded. I think this would break log analysis tools that depend on the status field being three digits, so probably not a good idea. 3. Tweaking the behavious of the %s format field thusly... 200 ==> good response, 499 ==> client closed the connection. This has two problems, first is 499 is not an official client error code. Second, we loose the original response status. I tend to like this one the best though. Perhaps we should create a new client error code to show this condition? Thoughts? Bill