[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Dreamweaver and SVN 1.2 Locking

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-05-10 19:59:57 CEST

On Apr 27, 2005, at 10:20 AM, Mark Phippard wrote:

> Ben Collins-Sussman <sussman@collab.net> wrote on 04/27/2005
> 10:39:37 AM:
>> On Apr 27, 2005, at 9:29 AM, Mark Phippard wrote:
>>> If you have the time and ability, another thing you might try is to
>>> see if
>>> you can get Dreamweaver to work with the generic Apache
>>> mod_dav_fs. If
>>> you can, then maybe the Subversion devs can learn something from
>>> that?
> I wonder if Julian has any info about Dreamweaver at greenbytes?

Mystery solved -- the Dreamweaver error you're seeing is indeed the
result of a recent svn 1.2.0-rc2 bug, we just discovered it and are
working to fix it now. I suspect it will be the main reason for
rc4. :-)

Specifically, Dreameweaver was sending a dav 'owner' field in the
lock request which looked like this:


And then later on, when it did a PROPFIND to retrieve the lock's
details, it wasn't getting back what it had put in, like it's
supposed to. mod_dav_svn was sending back:


In other words, mod_dav_svn was behaving as if a Subversion client
had created the lock, rather than a non-Subversion client.

Here's the dev@ thread describing the bug:


Thanks for finding this bug, Mark! The Dreamweaver HTTP trace was

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 10 20:05:29 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.