CODEWITHSUNDEEP
ms-wordms-officeoffice365ms-wopifsshttp
Ben Gan
Ben Gan

Reputation: 145

WOPI implementation without MS-FSSHTTP/COBALT

We are trying to implement a WOPI host without using CobaltCore dll against our Office Web Apps server. (implement in Java). All the information I found suggests that you have to implement MS-FSSHTTP in order to edit Word documents.

But, this is what I found on this page: Integrating with Office Online

Integrating with Office Online is relatively simple. You just need to do some HTML and JavaScript work, and set up a few simple REST endpoints. If you are familiar with existing Office protocols, note that you don’t have to implement the [MS-FSSHTTP]: File Synchronization via SOAP over HTTP Protocol (Cobalt)

There is also a sample implementation here

But I cannot get this to work when hitting our Office Web Apps Server (the header X-WOPI-Override equals to COBALT for Word docs).

  1. Does the information on that page only applies to scenarios where you are hitting Office Online?
  2. Is there a setting I have to change on the Office Web Apps Server so that it behaves like Excel file editing? On the CheckFileInfo, I tried setting SupportsCoauth=false and SupportsCobalt=false

Upvotes: 4

Views: 1589

Answers (1)

Ben Gan
Ben Gan

Reputation: 145

It looks like the document/page I referred to in my question is referring to the Office Online Server... which is a replacement of the Office Web Apps Server.

I downloaded the Preview of the Office Online Server here

When you compare the discovery.xml from both versions, the Word docx edit requirements are different:

Office Web Apps Server:
<action name="edit" ext="docx" requires="locks,cobalt,update"

Office Online Server:
<action name="edit" ext="docx" requires="locks,update"

I was able to implement Word Editing without referencing the Microsoft.CobaltCore.dll

Upvotes: 4

Related Questions