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

Re: httpd, mod_dav and LocationMatch

From: Michael Sweet <mike_at_easysw.com>
Date: 2004-11-18 21:55:21 CET

Marc Lalonde wrote:
> Hello,
> An issue has been raised a couple of times on the dev mailing list about
> using regexp in the Apache 'Location' directive to include/exclude urls
> to be passed to mod_dav (last time: msg 82012). Although GET requests
> (with a web browser) work well, svn clients trying to e.g. checkout a
> project get a "PROPFIND request failed". The funny part is that indeed
> something prepends the encoding of the regexp to the relative path to
> the project. During a checkout, the first two PROPFINDs get to Apache
> correctly but the third one is malformed:
> - - [17/Nov/2004:22:34:06 -0500] "PROPFIND /ophtalmo
> HTTP/1.1" 401 486
> - mlalonde [17/Nov/2004:22:34:06 -0500] "PROPFIND
> /ophtalmo HTTP/1.1" 207 709
> - - [17/Nov/2004:22:34:06 -0500] "PROPFIND
> (%5E/%5B%5Ec%5D.*)%7C(%5E/c%5B%5Eg%5D.*)%7C(%5E/cg%5B%5Ei%5D$)/ophtalmo/!svn/vcc/default
> HTTP/1.1" 400 311
> The farthest I've been able to go is on the server side (mod_dav),where
> repos->root_path in dav_svn_build_uri (./subversion/mod_dav_svn/util.c)
> is corrupt.The argument root_path passed to dav_svn_get_resource
> (repos.c) is also invalid. How is this last function called? Through a
> hook? Does anyone have any idea on the source of the problem?

I ran into a similar problem recently while testing our new
Subversion server (getting ever closer to eliminating CVS from our
projects! :)

Basically, I had erroneously put my Subversion repositories in
the same directory tree (in this case, .../svn.easysw.com/public/newsd)
as the rest of the server's non-SVN content. After re-reading the
Subversion book's coverage of Apache configuration, I found the
paragraph that said something along the lines of "don't put your
subversion repositories in the document root or Apache will get
confused". I moved the repo to a separate directory, updated the
paths in the Apache config files, and the PROPFIND error went away.

Sooo, make sure that your Subversion repository is not in a
subdirectory of your Apache web site directory. The organization
I will be using is:

                       /html -> Apache document root
                       /svn -> Subversion repositories

Michael Sweet, Easy Software Products           mike at easysw dot com
Internet Printing and Document Software          http://www.easysw.com
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 18 21:56:21 2004

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

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