Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 43478 invoked by uid 500); 25 Feb 2003 22:00:45 -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 43350 invoked from network); 25 Feb 2003 22:00:44 -0000 Date: Tue, 25 Feb 2003 16:59:41 -0500 (EST) From: Cliff Woolley X-X-Sender: root@deepthought.cs.virginia.edu To: dev@httpd.apache.org Subject: RE: mod_usertrack bugfix patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, 25 Feb 2003, Manni Wood wrote: > So does this mean that you now agree that I should be using a regexp to > find the cookie? I think that's what you mean. I'm still unclear why this requires a full-blown regex. Isn't all we really need to do to loop over the delimiters (semicolon and comma), remove whitespace, and then see if the next word (characters up to whitespace or an equal) matches the cookie name using strcmp()? --Cliff