Re: Problem using mod_dav_svn (returns 500 on non-svn requests)

I found some details about this issue.

When neither SVNPath, nor SVNParentPath are defined in a vhost, or alias, the mod_dav_svn prevents processing of all POST requests.

So it is no longer possible to have mod_dav_svn loaded in an apache instance used to serve other content (as modules are globals).

Le 18 oct. 2011 à 18:39, Jean-Daniel Dupas a écrit :

> Hello,
>
> After upgrading to svn 1.7, I encounter some very annoying issues.
> I have a web server with the following configuration:
>
> hostname/ : standard website
> hostname/svn: subversion repositories (using dav_svn)
> hostname/projects: other website.
>
> Before the update, this configuration were working fine. But after the update, anytime the server receives a POST request (whatever the path is), the dav_svn module try to handle it, and when it failed (always when the path does not start with /svn/...), it returns a 500 error (without logging anything in the error.log, which is an other issue).
>
> FWIW, the error is created and returned by the get_resource() function, in mod_dav_svn/repos.c.
>
> Is there something I can do to workaround this issue ?
>
> Thanks
>
> -- Jean-Daniel
>
>
>
>

-- Jean-Daniel
Received on 2011-10-18 18:55:02 CEST