Julian Foad wrote:
> On Thu, 2009-10-29, Dave Brown wrote:
>> In mod_dav_svn, when processing an SVNMasterURI directive,
>> check that mod_proxy is available in the httpd runtime.
>> Forwarding writes to a master from a slave requires
>> the mod_proxy handler, and when it isn't present, the
>> failure is ugly & opaque. Apache's core, default handler
>> sends back a "405 Not Allowed," for non-GET which looks
>> like an authz failure.
>> BTW, there's precedent for using ap_find_linked_module()
>> to check that module dependencies are present. Namely,
>> mod_rewrite looks for mod_proxy, and mod_authnz_ldap looks
>> for util_ldap.
>> * subversion/mod_dav_svn/mod_dav_svn.c
>> (SVNMasterURI_cmd): use ap_find_linked_module() to
>> ensure that mod_proxy is available
> Hi Dave.
> As I understood your explanation to me the other day:
> The problem is if you try to use the DAV write-through proxy, but don't
> have mod_proxy installed, then Subversion would issue an obscure and
> unhelpful error message at the time of trying to use it.
> The fix is twofold: check for mod_proxy being installed as soon as we
> know we need it, and issue a nice error message.
> This sounds great, exactly the sort of improvement we need.
> If nobody thinks of a problem with it, I will commit it. I will try to
> test it first, but I know you have done so.
Sorry, Dave, this patch (which I rather witnessed the conception of) skipped
past my radar somehow.
+1 to commit, Julian (with the small request that a blank line precede the
newly added comment).
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2009-11-05 15:36:37 CET