Aug 30 2022 04:27 AM
Hey
Don't know if this is the right forum but hope you can help.
I have a client who uses a custom WebDAV on-premise server together with Saperion as document handler, they do NOT use SharePoint.
They wish to upgrade from Office 2016 to Office 365, but we've run into some problemes which I suspect can have something to do with the WebDAV protocol.
I have used Fiddler to see how Word communicate with WebDAV and see no big difference other than the order of calls, and that 365 tries to make a POST call to what looks like SharePoint.
When we want to edit the document the following sequence of calls are made to the WebDAV server:
2016:
OPTIONS
HEAD (423 LOCK)
OPTIONS
LOCK (Response: Lockdiscorvery --- locktoken -- href -- opaquelocktoken)
GET
PROPFIND
HEAD
365:
OPTIONS
OPTIONS
HEAD (423 LOCK)
LOCK (Response: Lockdiscorvery --- locktoken -- href -- opaquelocktoken)
OPTIONS
GET
PROPFIND
HEAD
POST (/_api/web/GetFileByUrl(@v)/ListItemAllFields/GetSharingInformation) <- This I googled is a call to SharePoint, so it is ignored for now
In Word 2016 I am now able to do changes and save directly using WebDAV where it calls the following:
HEAD
LOCK (Refresh lock)
PUT
If I try and do the same with 365 I get an error saying the it couldn't succesfully save the data to the WebDAV path, and no calls were done using the WebDAV protocol.
I also observe that if a leave the document open in 2016 it will constantly refresh the locktoken, where this never happens in 365, which all points in the direction the Word 365 "forgets" that it has gotten a lock or just don't understand the response from the locktoken.
Are there any documentation on what exactly 365 wants as a response to the different WebDAV requests. I have found a document the discripte the newest WebDAV protocol in Office, and here it looks like we do forfill the requriments, and as shown this also works just fine for Word 2016.
I am more than happy to apply more information if needed.
Aug 29 2023 05:49 AM
Aug 29 2023 05:55 AM
Oct 20 2023 07:23 AM