[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.3 now blocking on path escaping in httpd operational logging

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-09-27 17:41:57 CEST

Justin Erenkrantz <justin@erenkrantz.com> writes:

> On Tue, Sep 27, 2005 at 11:01:12AM -0400, C. Michael Pilato wrote:
> > Justin Erenkrantz <justin@erenkrantz.com> writes:
> >
> > > > XML-escaping permits whitespace, meaning whitespace could not be our
> > > > delimiter. And mixing encodings is nasty.
> > >
> > > No, it doesn't. Those would still be quoted by virtue of the log format
> > > string that the admin would set.
> >
> > I'm ... not able to parse that. Sorry, Justin.
> The log format that the admin would use would look like (from Ben's
> initial email):


> Hope this clarifies things a bit. -- justin

It does, but not for the reasons you might assume. I had forgotten
that the tokens which make up an SVN-ACTION item (the action itself,
paths and revisions and such, etc.) are not first-class Apache log
tokens like USERNAME, TIMESTAMP, and, in fact, SVN-ACTION itself.

There was a time when I was talking with Ben about using multiple
envvars, like:


So that admins could customize their logs, but I forgot that we
dropped that because the complexity was overbearing.

C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 27 17:51:51 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.