dav_lock not enabled?
freebsd-apache at herveybayaustralia.com.au
Sun Aug 26 01:16:24 UTC 2012
On 08/24/12 22:08, olli hauer wrote:
> On 2012-08-24 12:29, Da Rock wrote:
>> On 08/24/12 01:59, olli hauer wrote:
>>> On 2012-08-23 17:31, Da Rock wrote:
>>>> On 08/24/12 00:16, olli hauer wrote:
>>>>> On 2012-08-23 14:45, Da Rock wrote:
>>>>>> I'm attempting to get a working webdav system going on my apache- and I'm having some issues with locking. Apparently my only means of doing this is using mod_dav_lock. And before any nay sayers pipe up, neither openoffice or libreoffice will work without it - just for starters.
>> Thanks Olli. I was thinking along those lines, but it was late and I was turning into a pumpkin :) Just couldn't quite get my head around all the details...
>> Cheers for the patch - it appears to all work btw.
> Thanks for the reports.
> I have to think if this module should be ON by default ...
> From http://httpd.apache.org/docs/2.2/mod/mod_dav_lock.html
> This module implements a generic locking API which can be used by any backend provider of mod_dav. It requires at least the service of mod_dav. *But without a backend provider which makes use of it, it's useless and should not be loaded into the server*. A sample backend module which actually utilizes mod_dav_lock is mod_dav_svn, the subversion provider module.
> *Note that mod_dav_fs does not need this generic locking module, because it uses its own more specialized version.*
> In order to make mod_dav_lock functional, you just have to specify the location of the lock database using the DavGenericLockDB directive described below.
> So this explains why subversion can handle locks even without the module but why does libre/open-office need the module?
> Shouldn't libre/open-office work properly with mod_fav_fs ??
I'm just going through this now; libreoffice has the ability to access
webdav directly but because of certificate issues it won't (besides, its
just not easy user wise), so I'm using wdfs to mount the store. wdfs
appears to hold the key here now, I've gone through everything else.
I'm looking at the logs and debug output from wdfs, and it appears to be
locking, retrieving, locking again (x2), which apache is returning a 423
(normal behaviour), but wdfs is reading as somebody else has it and
returns a readonly to the app. This is happening across all apps now as
At least it is locking now, I checked this with cadaver and it appears
normal with the dav_lock enabled.
I'm just reviewing the code for wdfs to see why it is behaving this way;
an interesting point is that locking is not enabled by default with
wdfs. That causes *office to go into coniptions and misbehave, but it
may be disabled due to the issues here. Wierd... can't find much in the
way of support because the site is mainly in german which I can't quite
read :) so I've let the author know my findings so far. See how it goes...
Thanks again Olli. With regards turning on the module in the build, I'd
say to just have it as an option or even just a knob that can be enabled
when required. I can't imagine there'd be many users out there besides
More information about the freebsd-apache