Version Control with Subversion, 2nd Edition

mod_dav_svn Configuration Directives

This section covers Apache configuration directives for serving Subversion repositories through the Apache HTTP Server. We will briefly describe each Subversion Apache configuration directive here. For an in-depth description of configuring Apache with Subversion, see httpd, the Apache HTTP Server.

Directives

These are the httpd.conf directives that apply to mod_dav_svn:

DAV svn

Must be included in any Directory or Location block for a Subversion repository. It tells httpd to use the Subversion backend for mod_dav to handle all requests.

SVNAllowBulkUpdates On|Off

Toggles support for all-inclusive responses to update-style REPORT requests. Subversion clients use REPORT requests to get information about directory tree checkouts and updates from mod_dav_svn. They can ask the server to send that information in one of two ways: with the entirety of the tree’s information in one massive response, or with a skelta (a skeletal representation of a tree delta), which contains just enough information for the client to know what additional data to request from the server. When this directive is included with a value of Off, mod_dav_svn will only ever respond to these REPORT requests with skelta responses, regardless of the type of responses requested by the client.

Most folks won’t need to use this directive at all. It primarily exists for administrators who wish—for security or auditing reasons—to force Subversion clients to fetch individually all the files ...