Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Tue, 9 Dec 2008 11:21:07 -0500
From: "Mark H. Wood" <mwood@IUPUI.Edu>
To: users@httpd.apache.org
Message-ID: <20081209162107.GA8572@IUPUI.Edu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4"
Content-Disposition: inline
User-Agent: Mutt/1.5.16 (2007-06-09)
Subject: [users@httpd] Specification for Common, Combined log file formats?

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

I need to build a gadget to extract information from HTTPD logs.
Various sources (including the Apache HTTPD 2.2 documentations) claim
that at least the Common Log Format is standardized, but I haven't
been able to find the standard itself.  Most of the format is clear,
but I have one burning question:  do I have to worry about quotes
within the three (or, according to some sources, four) quoted fields
of a Combined record?  And if so, how to handle them?

I presume that these three (or four) strings are URL-encoded, but it
would be nice to see a standard which says that this must be so.

--=20
Mark H. Wood, Lead System Programmer   mwood@IUPUI.Edu
Friends don't let friends publish revisable-form documents.

--YiEDa0DAkWCtVeE4
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkk+mvMACgkQs/NR4JuTKG/P6gCgkCgVbllxPEovT5fm86qsJ04L
64QAn2kSU24Qw39dEMimsrADb2TJUHgw
=sINS
-----END PGP SIGNATURE-----

--YiEDa0DAkWCtVeE4--