On 11/15/2012 08:49 AM, Joe Schaefer wrote: > Sure it can be done via config directives: > just set an env var whenever some request > is inconsequential and server admins can > configure their logging to ignore that request. > We already do that for svn operation logging.
I've been considering the same sorts of approaches recently (as a result of this thread). But one thing has me bothered: from the server's point of view, there's no meaningful difference between "a GET that's part of a checkout/update" and "a GET that's part of some other non-update-y operation". Does that mean that we give the client the power to mark particular GET requests as "below radar"? That doesn't seem very ... audit-friendly. (Granted, no one is forcing the server admin to ignore said GET requests.) If we don't feel comfortable giving the client this power, then I think our only option is to advise admins to ignore all GET requests aimed at Subversion repositories (which has the bonus feature of not requiring any work on our part). -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Enterprise Cloud Development
signature.asc
Description: OpenPGP digital signature
