Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of ph1@openstrike.co.uk
 designates 89.16.177.71 as permitted sender)
Date: Sat, 27 Jul 2013 09:29:01 +0100
From: Pete Houston <ph1@openstrike.co.uk>
To: users@httpd.apache.org
Message-ID: <20130727082901.GA1747@palma.openstrike.co.uk>
References: <1AE6C881-47F1-495B-BE38-0ABADC52C080@redfish-solutions.com>
 <51F0EDA3.3050407@globdesign.com>
 <OF26902E6B.B59A7E76-ON88257BB4.0011E6D7-88257BB4.00138B5F@LocalDomain>
 <20130726074700.GC1793@palma.openstrike.co.uk>
 <OFEE463D97.8FB4D61C-ON88257BB4.006AEEBA-88257BB4.006C00E3@LocalDomain>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp"
Content-Disposition: inline
In-Reply-To: 
 <OFEE463D97.8FB4D61C-ON88257BB4.006AEEBA-88257BB4.006C00E3@LocalDomain>
Organization: Openstrike
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [users@httpd] Logging Base64 decoded info in access_log

--17pEHd4RhPHOinZp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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 cookie.

I do not see the advantage in doing it in real time over
post-processing. The docs are pretty clear on this too.

http://httpd.apache.org/docs/2.4/logs.html#piped says

	As with conditional logging, piped logs are a very powerful tool,
	but they should not be used where a simpler solution like off-line
	post-processing is available.

which is good advice.

> Piped logs is an option I did not consider even though I am currently usi=
ng
> it for logs rotation. Can you suggest how I can achieve what you are
> proposing w/o loosing out on the log rotation functionality.
>=20
> I have the following in my httpd config:
>=20
> -------
> CustomLog "|/opt/apache/bin/rotatelogs /opt/apache/logs/access_log 86400"
> combined env=3D!dontlog
>=20
> #where dontlog are a couple of load balancers IP address I want to keep o=
ut
> of the access logs.
>=20
> -----------

If you go against the advice in the documentation and decide to do it
with piped logs just use something like=20

	CustomLog "|/path/to/filterprog | /opt/apache/bin/rotatelogs /opt/apache/l=
ogs/access_log 86400" combined env=3D!dontlog

And remember the docs also say:

	Piped log processes are spawned by the parent Apache httpd process,
	and inherit the userid of that process. This means that piped log
	programs usually run as root. It is therefore very important to keep
	the programs simple and secure.

Good luck,

Pete
--=20
Openstrike - improving business through open source
http://www.openstrike.co.uk/ or call 01722 770036 / 07092 020107

--17pEHd4RhPHOinZp
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAlHzhM0ACgkQdzfnYmsKt52fWgCg0bCqvtxN2PwV8MoQglwpzhDw
Xw8AoJDo7J6JGgkkg6IFnY0FKWpZUR8s
=Yyq6
-----END PGP SIGNATURE-----

--17pEHd4RhPHOinZp--