[SVN-3860] commits from out-of-date slave fails

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: trunk
• Fix Version/s: 1.10-consider
• Component/s: unknown
• Assignee: Unassigned
• Reporter: Subversion Importer
• Created: 19/Apr/11 06:30
• Updated: 19/Feb/15 14:52

Description

In a Master/Slave write-thru-proxy setup, if the slave is behind the master by
one or more revisions, certain write operations fail.

Example:

Master is at r100 and slave is at r99.
c100 was a commit that modified ^/branches/branch1/somefile

The following commands will fail:
1. svn cp ^/trunk ^/branches/branch2 (from WC of slave)
2. svn cp SLAVE_URL/trunk SLAVE_URL/branches/branch2 (same as 1?)
3. svn mkdir ^/branches/dir (from WC of slave)
4. svn mkdir SLAVE_URL/branches/dir (same as 3?)

I have submitted a test-case to the dev@ list that showcases the "svn cp" failure. 

N.B: This failure occurs for both neon and serf using HTTPV1. Only Neon fails
over HTTPV2, serf passes.

Original issue reported by arwin