On 28/07/2013 3:36 AM, "Rainer Jung" wrote:
>
> On 27.07.2013 10:29, Pete Houston wrote:
> > On Fri, Jul 26, 2013 at 12:39:37PM -0700, Jignesh Badani wrote:
> >> Thanks Pete, yes, post processing the log file nightly is the option I
was
> >> considering. I am doing it currently on a per request ba
On 27.07.2013 10:29, Pete Houston wrote:
> On Fri, Jul 26, 2013 at 12:39:37PM -0700, Jignesh Badani wrote:
>> Thanks Pete, yes, post processing the log file nightly is the option I was
>> considering. I am doing it currently on a per request basis. But I was
>> hoping to avoid it if I could do it i
On Fri, Jul 26, 2013 at 12:39:37PM -0700, Jignesh Badani wrote:
> Thanks Pete, yes, post processing the log file nightly is the option I was
> considering. I am doing it currently on a per request basis. But I was
> hoping to avoid it if I could do it in real time by calling on B64 decode
> on the
og
#where dontlog are a couple of load balancers IP address I want to keep out
of the access logs.
---
regards
-Jigs
From: Pete Houston
To: users@httpd.apache.org,
Date: 07/26/2013 12:47 AM
Subject: Re: [users@httpd] Logging Base64 decoded info in access_log
Hi Ji
Hi Jigs,
Maybe I'm missing something, but why not just post-process the logs?
Alternatively if you need this done in real-time for some reason you can
use piped logs and process them in-line that way.
Good luck with the management,
Pete
--
Openstrike - improving business through open source
ht
Hello, we have a custom user tracker cookie which is currently Base64
encoded and gets tacked along to each request in the access log.
We now have a new requirement to store the decoded value in the access log
instead.
So cookie gets written to the user's browser encoded, but when a user makes
a
