Why isn't Office sending the OPTIONS request to my WebDav server?

Kate Glickman 1 Reputation point
2025-08-11T19:53:47.8466667+00:00

We have implemented a WebDav server in our product using the following protocol

https://learn.microsoft.com/en-us/openspecs/office_protocols/MS-OCPROTO/2d268a23-420b-4339-8c56-9e4f8a924171

In step 1 of the spec, it says "The protocol client sends an HTTP OPTIONS request to the folder that contains the file..."

We have a customer who is trying to use this integration in our product. It works fine in one of their environments but does not work in their other environment. They are using the same client machine in both cases. The Fiddler log shows that the OPTIONS request is never happening in the non-working case.

In the past, we've seen issues when there is something wrong with the certificate. However, we have compared the certificates in the two environments and have not found a problem.

Is there another reason why the OPTIONS request would not be sent to the server?

Microsoft 365 and Office | Open Specifications
Microsoft 365 and Office | Open Specifications
Technical documents for protocols, computer languages, standards support, and data portability. The goal with Open Specifications is to help developers open new opportunities to interoperate with Windows, SQL, Office, and SharePoint.
{count} votes

1 answer

Sort by: Most helpful
  1. Kate Glickman 1 Reputation point
    2025-08-27T15:23:36.1933333+00:00

    It turns out that our Fiddler was taken in an environment without Word installed and we had been making a lot of assumptions based on it. The problem is a blocked OPTIONS request, the most obvious answer. Sigh.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.