Question

I’ve got a custom WebDAV server, built using Sphoirum webdav server, that resides inside an ASP.NET MVC3 application. It’s a .Net 4.0 project.

The document repository is a SharePoint, where our MVC application is a front end to it, and exposes the whole thing via the WebDAV. Just to note we don’t have WebDAV publishing enabled on our IIS 7.5.

I’ve implemented the following HTTP verbs:

• Get
• Head
• Lock
• Options
• PropFind
• Put
• Unlock

Now, when I open a word document, it’s first in the read only mode. Getting the lock and into edit mode is successful, but when I want to save the changes in my document I get the following:

Your changes were saved but could not be uploaded because of an error.

The trick is that document is indeed saved correctly to the repository, and the response from our WebDAV server to word is HTTP/200 but the Word complains nonetheless.
I’ve also tried editing in Word directly from the SharePoint repository, just to confirm that my Office isn’t broken somehow – all works.

Here’s the response from PUT request when saving the document from Word:

HTTP/1.1 200 OK
Date: Tue, 06 Sep 2011 12:25:47 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
MicrosoftSharePointTeamServices: 12.0.0.6545
Last-Modified: Tue, 06 Sep 2011 12:25:47 GMT
ETag: "{F4A63494-D302-4C9B-9C57-D0CB0937A2B0},9"
ResourceTag: rt:F4A63494-D302-4C9B-9C57-D0CB0937A2B0@00000000009
X-MSDAVEXTLockTimeout: Second-3600
Lock-Token: opaquelocktoken:{F4A63494-D302-4C9B-9C57-D0CB0937A2B0}20110906T122532Z
Expires: Mon, 22 Aug 2011 12:25:47 GMT
Cache-Control: private,max-age=0
Content-Length: 0
Public-Extension: http://schemas.microsoft.com/repl-2
Set-Cookie: WSS_KeepSessionAuthenticated=40689; path=/

And here’s the same response, for the same document, from our WebDAV server:

HTTP/1.1 200 OK
Cache-Control: private,max-age=0
Content-Length: 0
Expires: Wed, 24 Aug 2011 08:03:28 GMT
Last-Modified: Wed, 07 Sep 2011 08:03:28 GMT
ETag: "{4a4331a8-7df6-43e6-bd5f-bb80765e83a2},1"
Server: Microsoft-IIS/7.5
MS-Author-Via: DAV
ResourceTag: rt:4a4331a8-7df6-43e6-bd5f-bb80765e83a2@00000000001
Lock-Token: opaquelocktoken:{4a4331a8-7df6-43e6-bd5f-bb80765e83a2}20110907T080328Z
X-MSDAVEXTLockTimeout: Second-3600
Public-Extension: http://schemas.microsoft.com/repl-2
MicrosoftSharePointTeamServices: 12.0.0.6545
Set-Cookie: WSS_KeepSessionAuthenticated=40689; path=/
X-Powered-By: ASP.NET
Date: Wed, 07 Sep 2011 08:03:27 GMT

So I’ve tried to mimic some of the headers SharePoint emits, like MicrosoftSharePointTeamServices but to no avail.

Answer 1

By the way, I found the bug in Sphorium webdav that was causing this. The bug was in the method DavLockBase_InternalProcessDavRequest() and the incorrect line of code was:

string[] _lockTokens = this.RequestLock.GetLockTokens();

which should be:

string[] _lockTokens = this.ResponseLock.GetLockTokens();

After that change, saving files in Word 2010 worked fine.