2.2 Message Syntax

  • Article

The extension headers in this protocol conform to the form and behavior of other custom HTTP headers, as specified in [RFC2616] section 4.2. They are consistent with the WebDAV Protocol verbs and headers, as specified in [RFC4918] sections 8 and 9.

The following header extensions are specified in this section:

  • The X-MSDAVEXT response header has been added to the OPTIONS response and indicates support for the extensions that are covered in this document, as specified in section 2.2.1.

  • The Translate request header allows the client to request the source of an entity, as specified in section 2.2.2.

  • The X-MSDAVEXT_ERROR response header provides a mechanism for extended error handling, as specified in section 2.2.3.

  • The X-MSDAVEXTLockTimeout request/response header enables bundling of LOCK information (as specified in [RFC4918] section 8.10) with GET, PUT, and POST messages, as specified in section 2.2.4.1.

  • The Lock-Token request/response header enables bundling of LOCK information with GET, PUT, and POST messages, as specified in section 2.2.4.2.

  • The Ms-Echo-Request header is sent by the server when returning a 449 Retry With status, as specified in section 2.2.7.

  • The Ms-Echo-Reply header is sent by the client when making a request in response to a 449 Retry With status, as specified in section 2.2.8.

The following new content type is specified in this extension:

  • The Multipart/MSDAVEXTPrefixEncoded content type allows entity properties and entity content to be bundled in a single message, as specified in section 2.2.5.

The following new status code is specified in this extension:

  • The 449 Retry With status code allows the server to indicate that the request did not contain sufficient information and needs to be retried by the client, as specified in section 2.2.6.