[SVN-916] disallow PROPPATCH on deltaV baselines

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: all
• Fix Version/s: 2.0-consider
• Component/s: mod_dav_svn

Environment

other

• Assignee: Unassigned
• Reporter: Ben Collins-Sussman
• Created: 07/Oct/02 23:37
• Updated: 13/May/11 18:15

Description

In order to make 'svn propset' work over DeltaV on revision
properties, we had to violate the DeltaV spec.

The problem is that DeltaV doesn't have any notion of unversioned
properties... no notion, anywhere at all, on anything.  If you
PROPPATCH something, then a new version of *something* is supposed to
be created.

We've mapped the DeltaV notion of 'baseline' to a subversion
'revision'.  Our hack is to tweak mod_dav_svn so that you can actually
PROPPATCH a baseline, even though it's not a working resource, and
*not* create a new baseline as a result.

This is dangerous in two ways:  we're opening a possible hole in our
server, whereby another deltaV client wouldn't get an error when it
should.  Also, if somebody tries to use an svn client against some
other deltaV server, they're going to accidentally start creating new
baselines all over the place.  (In the future, we can prevent that by
having ra_dav check that the baseline's 'DAV:auto-version' property
isn't going to create a new baseline automagically.)

Anyway, this is really an issue for svn 2.0, which we dub the 'deltaV
interoperability' release.  But I want this issue here, so our source
comments can refer to it.