Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: neutral (athena.apache.org: 209.85.198.246 is neither permitted
 nor denied by domain of jarmstrong@bepress.com)
MIME-Version: 1.0
Date: Mon, 16 Mar 2009 17:11:38 -0700
Message-ID: <8f32497c0903161711x23c78b4dra6ee59836d2731bf@mail.gmail.com>
From: John Armstrong <jarmstrong@bepress.com>
To: users@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [users@httpd] Cookie tracking question

I have inherited an old, fragile codebase that uses CookieTracking. Great!

Except that when they implemented it they used

%{Cookie}i which outputs the cookie as 'cookiename=cookievalue' in the
logfile. It also ignores the first hit since its a header based
cookie, not a module based cookie, and we lose hits.

So, we decided to change to %{Cookie}n so our first hit logs.
Unfortunately, this outputs as 'cookievalue' so our
SuperTerrificTotallyCustomAndFragile log analysis software breaks
since it can't parse the unique user out of the logfile with the
cookie name.

Anyone know of a patch or a tweak that will get %{Cookie}n to output
'cookiename=cookievalue'?

Thanks-
John

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org