Choosing Between svnserve and Apache HTTPD for Subversion Access
Decide whether to use the lightweight svnserve daemon or Apache HTTPD with mod_dav_svn for your Subversion server, based on network, auth, and feature needs.
Loading…
ReadMeFeed / Community knowledge
#mod-dav-svn
Real questions. Useful conversations. Find the people who know your stack.
mod_dav_svn Apache connection pool vs svnserve Berkeley DB locks for burst concurrency
A deployment subject to intermittent bursts of Subversion client requests must choose between two documented server approaches for handling concurrency. mod_dav_svn relies on Apache's built-in connection pool, where acceptance is governed by server-wide client and timeout settings. svnserve with a Berkeley DB backend relies on DB_ENV lock tables and cache si
subversionsvnserve+SSH minimal footprint vs mod_dav_svn per-path authorization for constrained Subversion deployment
Design choice for a Subversion server under a resource-constrained host with a requirement for path-level access control. svnserve with SSH provides a minimal footprint and no external web server, but documented behavior shows it lacks per-path authorization. mod_dav_svn via Apache provides fine-grained access control through standard Apache directives, at t
mod_dav_svn returns generic 401 for expired LDAP passwords with no way to distinguish them from bad credentials
Goal I want a Subversion repository served by Apache httpd with mod_dav_svn and LDAP authentication to handle expired passwords in a predictable, least-privilege way: once a user's LDAP password expires, access should stop immediately and the failure should be identifiable as an expiration rather than a wrong password. Constraints and uncertainty From what I
