Return-Path: Delivered-To: apache-bugdb-archive@hyperreal.org Received: (qmail 19620 invoked by uid 6000); 17 Feb 1999 17:40:09 -0000 Received: (qmail 19190 invoked by uid 2001); 17 Feb 1999 17:40:00 -0000 Date: 17 Feb 1999 17:40:00 -0000 Message-ID: <19990217174000.19189.qmail@hyperreal.org> To: apache-bugdb@apache.org Cc: apache-bugdb@apache.org, From: Michael Kennedy Subject: RE: mod_usertrack/3909: mod_usertrack cookie logging isn't loggin g cookie, it's logging something else. Reply-To: Michael Kennedy Sender: apache-bugdb-owner@apache.org Precedence: bulk The following reply was made to PR mod_usertrack/3909; it has been noted by GNATS. From: Michael Kennedy To: apbugs@hyperreal.org, apache-bugdb@apache.org Cc: Subject: RE: mod_usertrack/3909: mod_usertrack cookie logging isn't loggin g cookie, it's logging something else. Date: Wed, 17 Feb 1999 12:37:47 -0500 Please ignore this, I've described the wrong problem. It goes as follows: We've got Apache 1.3.4 set up as a reverse proxy caching server. The usertrack module is generating and logging new IDs for each incoming request, but the cookies are NOT being issued to end users. Is this a bug? I think it should issue cookies, because all of our logging needs to be done on this server. > -----Original Message----- > From: apbugs@hyperreal.org [SMTP:apbugs@hyperreal.org] > Sent: Wednesday, February 17, 1999 11:40 AM > To: michael@toronto.com > Subject: Re: mod_usertrack/3909: mod_usertrack cookie logging isn't > logging cookie, it's logging something else. > > Thank you very much for your problem report. > It has the internal identification `mod_usertrack/3909'. > The individual assigned to look at your > report is: apache. > > >Category: mod_usertrack > >Responsible: apache > >Synopsis: mod_usertrack cookie logging isn't logging cookie, it's > logging something else. > >Arrival-Date: Wed Feb 17 08:40:00 PST 1999