Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 58466 invoked from network); 2 Mar 2004 06:08:55 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Mar 2004 06:08:55 -0000 Received: (qmail 77172 invoked by uid 500); 2 Mar 2004 06:08:22 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 77086 invoked by uid 500); 2 Mar 2004 06:08:21 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 77004 invoked from network); 2 Mar 2004 06:08:20 -0000 Received: from unknown (HELO scotch.ics.uci.edu) (128.195.24.168) by daedalus.apache.org with SMTP; 2 Mar 2004 06:08:20 -0000 Received: from [10.0.1.91] (pv106211.reshsg.uci.edu [128.195.106.211]) (authenticated bits=0) by scotch.ics.uci.edu (8.12.6/8.12.6) with ESMTP id i2268McJ027352 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 1 Mar 2004 22:08:30 -0800 (PST) Date: Mon, 01 Mar 2004 22:08:24 -0800 From: Justin Erenkrantz To: dev@httpd.apache.org Subject: Re: how to tell one request from another inside a connection filter over keep-alive connection Message-ID: <2147483647.1078178904@localhost> In-Reply-To: <40440B2D.9020508@stason.org> References: <400C9BFA.6050202@stason.org> <40440B2D.9020508@stason.org> X-Mailer: Mulberry/3.1.2 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=unavailable version=2.70-r6256 X-Spam-Checker-Version: SpamAssassin 2.70-r6256 (2004-01-23) on scotch.ics.uci.edu X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N --On Monday, March 1, 2004 8:18 PM -0800 Stas Bekman wrote: > Answering my own question, the solution is to use conn->keepalives counter > which is incremented at the end of each request. By storing the previous > count and comparing with the current count one can tell when a new request > is coming in over the keepalive connection. This technique is now documented > in the mod_perl land: Sorry, but I think something is off here. Why should a connection-level filter know about HTTP requests? -- justin