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

Limiting Subversion noise in apache logs

From: <kmradke_at_rockwellcollins.com>
Date: Tue, 11 Sep 2012 16:45:22 -0500

I've always been slightly annoyed with Apache 401 "unauthorized" log
when accessing a Subversion repository. I realize these are part of the
standard authentication "handshake" via the http protocol.
(Always ask anonymously first...)

I also realize that mod_dav_svn can now provide a custom log file, but I
my apache logs. On a busy server, these can get to be tens of gigabytes
day. I'm not aware of a way to limit log entries based upon return status

As a test, I think I have been able to abuse the rewrite_module to get rid
of these apache 401 log entries and I was wondering if any
gurus could poke holes in why this either doesn't work or shouldn't be

<IfModule rewrite_module>
  # Do not log authentication required responses
  RewriteEngine On
  RewriteCond %{LA-U:REMOTE_USER} =""
  RewriteCond %{REQUEST_URI} !-U
  RewriteRule .* - [Last, ENV=dontlog:1]

<IfModule log_config_module>
  LogFormat "%h %l %u %t \"%r\" %>s %b" common
  CustomLog "logs/access.log" common env=!dontlog

I'm aware the sub-request for the last RewriteCond line is expensive. I'm
hopeful the other RewriteCond lines would short circuit most of the server
accesses. Does Subversion create any connections with something
other than an initial OPTIONS request? I only trivially tested neon. I
that condition as a hopeful performance improvement.

And yes, as I stated above, I realize Subversion can create it's own
custom log, but using that removes the fun in this experiment...

Kevin R.
Received on 2012-09-11 23:45:59 CEST

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

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