I see other requests that I would expect to have had a lock reference, but the resource in question had already been UNLOCKED beforehand - immediately after the LOCK. I can only find some PUT requests that actually do come after a LOCK and it they have the required lock If header. Are you sure the resource is still locked? One odd thing about the Finder is that most of its LOCK commands are immediately followed by UNLOCK, with no operation in between. I can see instances of the Finder issuing a LOCK and then a PUT, but the PUT always has an If header.
I don't claim to understand the reasoning behind the Finder's requests, but I can't confirm what you are seeing. Well, I've spent the last 3 months writing my own webdav server specifically for use with the Finder. Has anyone else seen this problem and have a solution ? I confirmed that this is not a problem with 10.8 or earlier versions. Sandbox: QuickLookSatelli(41334) deny network-outbound /private/tmp/.webdavUDS.YlINRf
Looking at client webdav server traffic, it appears that after acquiring LOCK on a file, client is not supplying lock token in subsequent requests to server, resulting in 423 responses on subsequent operations.Īccording to webdav spec, client needs to supply file lock-token in subsequent commands to server.Īt this point, webdav mount also gets disconnected with following error in dmesg.
Since OS X 10.9 upgrade, many webdav actions including dragging a file onto a webdav mount using Finder and editing files using MS office applications (Microsoft Word, Office, Powerpoint) have stopped working. My company provides a webdav server solution for OS X webdav clients.