BPROPFIND Method

BPROPFIND 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 WebDAVBPROPFIND Method is similar to the PROPFIND Method but it is used to retrieve the properties of one or more target resources.

The request body for the BPROPFIND Method is the same as the PROPFIND Method with the addition of the target XML Element at the same level as the prop XML Element.

When a PROPFIND Method or a BPROPFIND Method request contains a Brief Header with a value of "t", every propstat XML Element with a status of 404 (Not Found) is omitted from the 207 (Multi-Status) response.

The BPROPFIND Method is not supported in transactions.

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 does not have access to the property.
404 (Not Found) The property could not be found.
424 (Method Failure) The method cannot be supported in a transaction.

Example

The following example illustrates a WebDAVBPROPFIND Method being successfully used to retrieve the wordcount, editor, and author properties on file1 and file2.

Request

BPROPFIND /container/ HTTP/1.1
Host: www.contoso.com
Depth: 0
Content-type: text/xml
Content-Length: xxxx

<?xml version="1.0" ?>
<D:propfind xmlns:D="DAV:" xmlns:R="https://www.contoso.com/schema/">
        <D:target>
		<D:href>file1</D:href>
		<D:href>file2</D:href>
        </D:target>
        <D:prop>
                <R:wordcount/>
                <R:author/>
                <R:editor/>
        </D:prop>
</D:propfind>

Response

HTTP/1.1 207 Multi-Status
Content-Type: text/xml
Content-Length: xxxx

<?xml version="1.0" ?>
<D:multistatus xmlns:D="DAV:" xmlns:R="https://www.contoso.com/schema/">
  <D:response>
       <D:href>https://www.contoso.com/container/file1</D:href>
       <D:propstat>
            <D:status>HTTP/1.1 200 OK</D:status>
            <D:prop>
                 <R:wordcount>2037</R:wordcount>
                 <R:author>Rob Caron</R:author>
                 <R:editor>Jessup Meng</R:editor>
            </D:prop>
       </D:propstat>
  </D:response>
  <D:response>
       <D:href>https://www.contoso.com/container/file2</D:href>
       <D:propstat>
            <D:prop>
                 <R:wordcount>5782</R:wordcount>
                 <R:author>Kim Hightower</R:author>
                 <R:editor>Wendy Vasse</R:editor>
            </D:prop>
            <D:status>HTTP/1.1 200 OK</D:status>
       </D:propstat>
  </D:response>
</D:multistatus>

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

This topic last updated: December 2002

Build: June 2007 (2007.618.1)

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