Re: can mod_dav_svn 1.5 deny access from earlier clients?
> (copied to dev@... as I think this one's a defect).
> Except that this appears to be broken if you're using mod_dav_svn 1.5.0.
> As previously posted by Jacky-10:
>> I notice the commit action in mod_dav_svn involves a few steps. The
>> first step uses OPTIONS which includes DAV: .../mergeinfo in the http
>> header. But the following steps (PROPFIND, MKACTIVITY) don't include
>> this header which seems to make svn server calling start-commit script
>> without mergeinfo capability."
> I've confirmed this in an ethereal session (attached) - the capabilities
> parameters are listed in the DAV: parameters passed to the HTTP request
> but are not being passed through to the start-commit script.
> OPTIONS /svn/repos/david.x.grierson/trunk/src HTTP/1.1
> Host: 192.168.56.128
> User-Agent: SVN/1.5.0
> Connect: TE, Keep-Alive
> TE: trailers
> DAV: http://subversion.tigris.org/xmlns/dav/svn/depth
> DAV: http://subversion.tigris.org/xmlns/dav/svn/mergeinfo
> DAV: http://subversion.tigris.org/xmlns/dav/svn/log-revprops
> Accept-Encoding: gzip
> Whereas the the start-commit output is:
> svn: Commit failed (details follow):
> svn: Commit blocked by start-commit hook (exit code 1) with output:
> Repo path: [/opt/svnroot/david.x.grierson]
> Username: 
> Capabilities: 
> Sorry - you are using a pre-1.5.x Subversion client - exiting!
> start-commit hook script and ethereal session attached.
> I'll raise this as a defect against 1.5.0 - I don't have a build of 1.5.1
> yet so can't confirm whether it's still present in that.
We would much prefer if you (or someone else) could see if the bug is still
present in 1.5.1 before filing an issue. It really helps to keep the issue
tracker clean. I know we did fix a few things related to authz over dav in
1.5.1, and wonder if this is one of them.
Received on 2008-08-04 16:32:38 CEST
This is an archived mail posted to the Subversion Dev