Share via

PROPPATCH Method

  • Article

PROPPATCH Method

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release. The WebDAVPROPPATCH method sets properties for the resource at the specified destination Uniform Resource Identifier (URI). All property names must be scoped in the XML body using namespace URI references.

When a PROPPATCH method or a BPROPPATCH Method request contains a Brief Header with a value of "t", every propstat XML Element with a status of 200 (OK) is omitted from the 207 (Multi-Status) response. If all operations on all resources are completed successfully, the 200 (OK) response may be returned instead of a 207 (Multi-Status) response.

The PROPPATCH method may be included in the scope of a transaction by submitting a Transaction Header with a lock token that corresponds to that transaction.

Note  See Authentication and Security Using WebDAV for more information.

The list of WebDAV Protocol Status Codes in the following table is not comprehensive. For information about 500-level status codes, see WebDAV Status Codes: 500s.

Status Codes

The following are response codes that can be expected to be used in a 207 (Multi-Status) response for this method.

Status Code Meaning
200 (OK) The command succeeded.
403 (Forbidden) The client is unable to alter one of the properties.
409 (Conflict) The client has provided an inappropriate value for this property. For example, the client tried to set a read-only property.
423 (Locked) The destination resource is locked.
507 (Insufficient Storage) The server did not have enough storage space to record the property.

Examples

The following example illustrates a WebDAVPROPPATCH method.

Request

PROPPATCH /docs/myfile.doc HTTP/1.1
Host: www.contoso.com
Content-Type: text/xml
Content-Length: XXX
Translate: F

<?xml version="1.0"?>
<d:propertyupdate xmlns:d="DAV:" xmlns:o="urn:schemas-microsoft-com:office:office">
  <d:set>
    <d:prop>
      <o:Author>Douglas Groncki</o:Author>
    </d:prop>
  </d:set>
</d:propertyupdate>

Response

HTTP/1.1 207 Multi-Status
Server: Microsoft-IIS/5.0
Date: Wed, 04 Aug 1999 21:52:58 GMT
Content-Type: text/xml
Content-Length: 310

<?xml version="1.0"?>
<a:multistatus xmlns:b="urn:schemas-microsoft-com:office:office" xmlns:a="DAV:">
  <a:response>
    <a:href>https://www.contoso.com/docs/myfile.doc</a:href>
    <a:propstat>
      <a:status>HTTP/1.1 200 OK</a:status>
        <a:prop>
          <b:Author/>
        </a:prop>
    </a:propstat>
  </a:response>
</a:multistatus>

Send us your feedback about the Microsoft Exchange Server 2003 SDK.

This topic last updated: June 2004

Build: June 2007 (2007.618.1)

© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.