none
WOPI - CoAuth of Word documents RRS feed

  • Question

  • While testing our WOPI host implementation I'm facing an issue with co-authoring.

    The second user (no difference is a different or the same use opening a second browser tab) cannot edit the document because the WOPI host is receiving lock requests with a different lock token and the WOPI host is returning a 409/Conflict.

    What do we need to change in order to make co-authoring work?

    On some other thread in here I was reading about that it will only work if the host is reachable via https - I'm currently developing this on localhost using http. Could that really be the reason?

    THX

    Tuesday, July 10, 2018 11:19 AM

Answers

  • Hi Tom,
     
    I wanted to respond back to the forum post with the latest status. We directed you to the WOPI Validator (https://github.com/Microsoft/wopi-validator-core) and you are using the utility to test your WOPI implementation. If any questions related to the results of running the WOPI Validator or implementation questions, feel free to contact the Open Specifications Support Team (https://msdn.microsoft.com/en-us/openspecifications/cc816063) or by posting here on the forum.
     
    Will Gregg | open specifications
    Friday, August 10, 2018 10:02 PM
    Moderator

All replies

  • Hi DeepDiver1975,

    Thank you for posting your question regarding CoAuth. A member of the Open Specifications Support team will be responding to your post to assist further.

    Thanks



    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Tuesday, July 10, 2018 7:06 PM
  • Hi Tom,

    Thank you for posting your question regarding whether the co-authoring issues you are encountering are related to your use of HTTP vs HTTPS. 

    To help us investigate, can you please tell us in which version of Office Online you observe this problem. Every response from our server will include an X-OfficeVersion header with the version of the server. Please share that version number with us. 

    Will Gregg | open specifications

    Tuesday, July 10, 2018 7:56 PM
    Moderator
  • Thanks for the hint about the response header!

    Here we go:

    x-officeversion:

    16.0.8471.8525

    THX,

    Tom

    Wednesday, July 11, 2018 10:23 AM
  • Hi Tom,

    Thank you for provided the X-officeversion response header value. 

    I am investigating whether the usage of HTTP could be the cause of the problem with coauthoring. In general we encourage usage of HTTPS for security reasons, so I am unaware of any requirements on HTTPS for coauthoring, but I am checking.

    Once I confirm or deny I may need to request a Fiddler trace of the sequence that leads to failure. But let me check before I have you provide that. 

    Will Gregg | Open Specifications

    Wednesday, July 11, 2018 7:51 PM
    Moderator
  • Tom,

    A quick question. You mention LOCALHOST. Are you hosting OOS and your WOPI HOST on the same machine? If so, that turns out to be an unsupported scenario and does produce unexpected behavior. 

    Will Gregg | open specifications

    Wednesday, July 11, 2018 10:45 PM
    Moderator
  • I have the WOPI host running on my laptop and the web server has only http setup.

    Office Online is installed on the corporate network.

    Thanks,

    Tomm

    Thursday, July 12, 2018 7:44 AM
  • Hi Tom,

    Thanks for clarifying the environment for me. Rules out that same machine issues that can occur. Keep in mind that running seperate VMs for the OOS server and the WOPI Host on the same VM server is totally appropriate. 

    Let me finish investigating the HTTP vs HTTPS side of stuff. As I noted previously I am not aware of any requirement, but its always worth checking. 

    Will Gregg | open specifications

    Thursday, July 12, 2018 12:39 PM
    Moderator
  • Hi Tom,

    I verified that there is no explicit requirement to use HTTPS for the WOPI protocol. It is simply a strong recommendation for security purposes. 

    We're going to need to collect Fiddler traces and ULS Logs for the failing WOPI scenario to debug further.

    Can you please email me at dochelp @ microsoft.com, just reference this thread, so I can provide you the information you'll need to collect the logs and upload them me? 

    Once I have the logs, I will post back to the thread here to work through the issue with you. 

    Will Gregg | open specifications

    Thursday, July 12, 2018 5:56 PM
    Moderator
  • Hi Tom,

    Thank you for working with us to obtain the logs and traces we were asking for. I am circling back to the forum quickly to ensure the thread is updated to reflect the latest information.

    The cause of the original issue you posted appears to have been caused by an issue or corruption in the OOS configuration. That was worked through in obtaining the logs. Again, thank you for working with us to obtain the logs.

    The current issue you are encountering is a second instance not sync'ing changes in a co-authoring session. You have provided us logs for that issue and we are looking into it.

    Will Gregg | open specifications

    Thursday, August 2, 2018 2:29 PM
    Moderator
  • Hi Tom,
     
    I wanted to respond back to the forum post with the latest status. We directed you to the WOPI Validator (https://github.com/Microsoft/wopi-validator-core) and you are using the utility to test your WOPI implementation. If any questions related to the results of running the WOPI Validator or implementation questions, feel free to contact the Open Specifications Support Team (https://msdn.microsoft.com/en-us/openspecifications/cc816063) or by posting here on the forum.
     
    Will Gregg | open specifications
    Friday, August 10, 2018 10:02 PM
    Moderator
  • There has been an issue in our lock implementation - specifically the implementation of https://wopi.readthedocs.io/projects/wopirest/en/latest/files/UnlockAndRelock.html

    Thanks to this great tool https://github.com/Microsoft/wopi-validator-core we got the issue sorted out!

    Case closed! Thank you!

    Tuesday, August 14, 2018 2:38 PM