Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
1.5.x
-
None
Description
When a file has been renamed (svn mv) in one WC, trying to `svn up' a different WC of the same leads the client to try an OPTIONS for the repository root. When this happens in a repository where the root is protected through authz (for example, a repository where each user can see only their own directory) the client aborts when it receives "403 Forbidden". This was raised on the mailing list in a thread labeled "Issues with an authz-protected repository", see: http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1131969 See that post for a description for how to reproduce the problem. It might be related to Issue 3242, but for us it happens for an `svn mv' and the problem manifests itself through a bad OPTIONS rather than a PROPFIND. In the mentioned thread Mark Phippard said that In 1.5 it was changed so that it "anchors" the session at the common parent ... and this might be what happens in our case too -- we started to get this problem in 1.5.x, not before. (Also, I used `libsvn_ra_neon' for the component field above, but only because Stefan Sperling mentioned on the mailing list that this is where the code that performs the offending query lives. I don't know more than that.)
Original issue reported by elibarzilay
Attachments
Issue Links
- duplicates
-
SVN-3242 Subversion demands unnecessary access to parent directories of operations
- Closed