ttpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> " from the digest: users-digest-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>
--
John Armstrong
Vice Preside
d.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> " from the digest: users-digest-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>
--
John Armstrong
Vice Pres
lude those?
>
> Thanks,
> Mike
>
>
> On Wed, Apr 1, 2009 at 10:43 AM, John Armstrong
> wrote:
>>
>> We use relative url's to bypass this issue.
>>
>> It also prevents other 'backend URL leakage' and generally allows for
>> proper lo
-
> The official User-To-User support forum of the Apache HTTP Server Project.
> See http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> " from the digest: users-digest-unsubscr...@httpd.apache.org
>
a way
to track the user ID on the first hit(n) but also get the cookiename
(i).
It may not exist which is why I also asked if anyone knew of a patch
or alternative module that can accomplish this task.
John-
On Tue, Mar 17, 2009 at 6:33 AM, Krist van Besien
wrote:
> On Tue, Mar 17, 2009
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 w
