Received: (qmail 20442 invoked by uid 501); 6 Jun 2001 19:49:51 -0000 Message-Id: <20010606194951.20441.qmail@apache.org> Date: 6 Jun 2001 19:49:51 -0000 From: Mark Schwartz Reply-To: mschwartz@massmutual.com To: submit@bugz.apache.org Subject: CookieName directive doesn't work in primary server's vhost config X-Send-Pr-Version: 3.110 >Number: 7829 >Category: mod_usertrack >Synopsis: CookieName directive doesn't work in primary server's vhost config >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Jun 06 12:50:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: mschwartz@massmutual.com >Release: 1.3.12 >Organization: apache >Environment: SunOS 5.7 SunWSPro 4.2 compiler >Description: I am seeing a problem reported in a dejanews article from 2000/04/01. Here is the mail attachment from preeper@my-deja.com which contains an excellent summary of the issue: ******************************************************************************** I just upgraded to apache 1.3.12 and am using the dynamic libraries including mod_usertrack. In httpd.conf I use the following to set cookies in each virtual host: CookieTracking on CookieExpires "2 years" CookieName "mycookie" It seems to work fine for every virtual host except for the one that is also the main server... If I put it into the global server configuration, however, it then sets the cookie on every virtual host, which I definitely don't want to happen... I am setting the cookie right after the serveradmin directive... I can't put it in the area because then I can't use the cookieexpires and keeping the cookie only for the current session is useless to me... Anyone have any ideas. ****************************************************************************** >How-To-Repeat: see full description. >Fix: Sorry. I wish I did:-) >Release-Note: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]