Bug#242866: [Pound Mailing List] PROPFIND 501 Not Implemented - after upgrading from 1.8.2 to 1.9.4

[Sam Johnston <samjie@gmail.com>]

> > I just upgraded pound-1.8.2 to pound-1.9.4-1 on a Debian 3.1 serving
> > up subversion repository.
> >
> > I verified that pound.cfg (unmodified)  still contains these 2 entries:
> >
> > ExtendedHTTP    1
> > WebDAV          1
> >
> > After restarting pound, I get PROFIND 501 Not Implemented errors when
> > I try to access the repository.
> >
> > I installed pound-1.9.4-1 using apt-get (did not compile from source).
> >
> Well, turns out the prior version was compiled from source with
> --enable-msdav added.

I don't recall this ever having been the case for the Debian package
(see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=242066), but it
would be easy enough to verify - it's public information :)

Here were my comments on the issue back in August:

#242066: please enable DAV support
Apparently one also needs a config setting, but to be sure I trawled
through the code and found that the list of characters matched in
regular expressions is more lenient with this option enabled, even
when the config file setting is disabled. The functionality seems
useful enough to be included in pound proper (eg for subversion
support), even if without the extra characters. Ideally they would be
separate runtime options. This would no doubt require an amount of
work upstream though.

> To fix, just use dpkg-source and then dpkg-buildpackage after modifying
> ./debian/rules in the unpacked directory.

I would like to support subversion by default. My understanding of the
situation is this:

 - we enforce RFC compliance. this is good and i agree with it.
 - subversion should be RFC compliant - is it?
 - MSDAV is not RFC compliant and needs workarounds which have to be
enabled at compile time
 - currently subversion and msdav are bundled together under the same
compile time and config directives and as such I can't make a
subversion friendly package without also introducing potential
security issues associated with allowing MSDAV.

Please let me know if these assumptions are accurate,

Sam