6 Appendix A: Product Behavior

  • Article

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Windows 2000 operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system

  • Windows Server 2008 operating system

  • Windows 7 operating system

  • Windows Server 2008 R2 operating system

  • Windows 8 operating system

  • Windows Server 2012 operating system

  • Microsoft SharePoint Foundation 2010

  • Windows 8.1 operating system

  • Windows Server 2012 R2 operating system

  • Windows 10 operating system

  • Windows Server 2016 operating system

  • Windows Server operating system

  • Windows Server 2019 operating system

  • Windows Server 2022 operating system

  • Windows 11 operating system

  • Windows Server 2025 operating system

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2.2.1: The web server in IIS for Windows 2000, Windows XP, Windows Server 2003, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server operating system, Windows Server 2019, Windows Server 2022, and Windows Server 2025  can accept the Translate request header. This implementation accepts "f" and "F" as FALSE. Everything else, including omission of the header, is accepted as TRUE.

<2> Section 2.2.1:  The web server in IIS for Windows 2000, Windows XP, Windows Server 2003, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server operating system, Windows Server 2019, Windows Server 2022, and Windows Server 2025 can accept this header on all commands, while only honoring this header on GET commands.

<3> Section 2.2.3: This request header can be supported by the WebDAV server in IIS for Windows 2000, Windows XP, and Windows Server 2003.

<4> Section 2.2.4: This method can be supported by the WebDAV server in IIS for Windows 2000, Windows XP, and Windows Server 2003, and is used to pass queries to Windows Index Server.

<5> Section 2.2.5.1: The WebDAV server in IIS for Windows 2000, Windows XP, Windows Server 2003, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server operating system, Windows Server 2019, Windows Server 2022, and Windows Server 2025 return the additional iscollection and ishidden properties as "live" properties.

<6> Section 2.2.5.2: The WebDAV server in IIS for Windows 2000, Windows XP, and Windows Server 2003 does not support locking collections.

<7> Section 2.2.5.3: The WebDAV server in IIS for Windows 2000, Windows XP, Windows Server 2003, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server operating system, Windows Server 2019, Windows Server 2022, and Windows Server 2025  allows the use of multiple <d:prop></d:prop> elements to encapsulate multiple properties.

<8> Section 3.1.3: The WebDAV server in Windows 2000, Windows XP, Windows Server 2003, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server operating system, Windows Server 2019, Windows Server 2022, and Windows Server 2025 can return the MS-Author-Via: DAV response header if WebDAV is enabled on the server.

<9> Section 3.1.5.3: The Depth header field is used with several WebDAV commands. However, Windows implementations only support the "noroot" extension on two verbs: DELETE and PROPFIND. "1,noroot" is supported for PROPFIND and "infinity,noroot" is supported on DELETE. Attempting to specify "noroot" on other verbs that support the Depth header field will result in a "400 Bad Request" error being returned.

<10> Section 3.2.5.1: The WebDAV server in IIS for Windows 2000, Windows XP, and Windows Server 2003 requires WRITE access to the file to return the source of the file.

<11> Section 3.2.5.1: The WebDAV server in IIS for Windows 2000, Windows XP, Windows Server 2003, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server operating system, Windows Server 2019, Windows Server 2022, and Windows Server 2025  assumes the header as Translate: t by default.

<12> Section 3.2.5.2: The WebDAV server in IIS for Windows 2000, Windows XP, Windows Server 2003, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server operating system, Windows Server 2019, Windows Server 2022, and Windows Server 2025  can return the MS-Author-Via response header in response to an OPTIONS request.

<13> Section 3.2.5.3: The WebDAV server in IIS for Windows 2000, Windows XP, and Windows Server 2003 supports the Depth "noroot" request header extension.

<14> Section 3.2.5.4:  The WebDAV server in IIS for Windows 2000, Windows XP, and Windows Server 2003 supports the SEARCH method.

<15> Section 5.1:  For a Translate header value of FALSE, the WebDAV server in IIS for Windows 2000, Windows XP, and Windows Server 2003 requires WRITE access to return the source of the file.