3.2.5.1 Extensions to OPTIONS

A WebDAV Protocol: Microsoft theft Extensions-compliant server advertises its capabilities via headers returned in response to a client's OPTIONS request.<20>

The Allow entity header field, as specified in [RFC2616] section 14.7, of the OPTIONS response SHOULD include the methods supported by compliant WebDAV servers as well as the GETLIB extension method (section 2.2.5).

In addition to the headers normally returned by a WebDAV-compliant server to the OPTIONS request, as specified in [RFC2518], a server compliant with the WebDAV Protocol: Microsoft Extensions MUST respond with the MS-Author-Via header (section 2.2.7). The server MAY send the Document Management Server header (section 2.2.1) as specified below.<21>

A Public-Extension header with the schema http://schemas.microsoft.com/repl-2 SHOULD<22> be sent to provide the definitions for the XML tags Repl-uid and ResourceTag.

The MS-Author-Via header is specified in [MS-WDVSE]. A server implementing the WebDAV Protocol: Microsoft Extensions MUST include the DAV option in this header.

The Document Management Server header (section 2.2.1) SHOULD NOT be sent unless the server implements one or more of the capabilities listed (or other extended capabilities) in its implementation of the FrontPage Server Extensions: Website Management Protocol, as specified in [MC-FPSEWM]. The capabilities listed are not part of the WebDAV Protocol: Microsoft Extensions. They are listed in this header to inform clients capable of using the FrontPage Server Extensions: Website Management Protocol, as documented in [MC-FPSEWM].