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 NT

  • Windows 2000 Professional operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system

  • Windows Server 2008 operating system

  • Windows Server 2008 R2 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 1.7.1: Specific protocol versions implemented by FPSE and SharePoint, covered in [MC-FPSEWM] and [MS-FPSE], are listed in the following table:

Protocol version

FPSE version

SharePoint version

Windows-To-Windows behaviors: described in MS-FPSE

Broader behaviors: described in MC-FPSEWM

1.0.x.x

Vermeer FrontPage 1.0

n/a

No

No

1.1.x.x

Microsoft FrontPage 1.1

n/a

No

No

2.0.x.x

Microsoft FrontPage 97

n/a

No

No

3.0.x.x

Microsoft FrontPage 98

n/a

No

No

4.0.x.x

Microsoft FrontPage 2000

n/a

Yes

No

5.0.x.x

Microsoft FrontPage 2002

Windows SharePoint Team Services 1.0

Yes

No

6.0.x.x

n/a

Windows SharePoint Services 2.0

Yes

No

12.0.x.x

n/a

Windows SharePoint Services 3.0

Yes

Yes

14.0.x.x

n/a

Microsoft SharePoint Foundation 2010

Yes

Yes

15.0.x.x

n/a

Microsoft SharePoint Foundation 2013, Microsoft SharePoint Server 2016, Microsoft SharePoint Server 2019

n/a

n/a

<2> Section 2.2.2.2.5: If the version is at least SharePoint Foundation 2010, it does not implement the DOC-INFO-REQUEST type (section 2.2.2.2.15).

<3> Section 2.2.2.2.15: If the server version is at least SharePoint Foundation 2010, it does not implement this type.

<4> Section 2.2.2.2.18: The FrontPage Server Extensions: Website Management Protocol version 12.0 accepts this parameter.

<5> Section 2.2.2.2.18: The FrontPage Server Extensions: Website Management Protocol version 12.0 accepts this parameter.

<6> Section 2.2.2.2.18: The FrontPage Server Extensions: Website Management Protocol version 12.0 accepts this parameter and requires the requesting user to be a web administrator.

<7> Section 2.2.2.3.4: In FrontPage Server Extensions: Website Management Protocol Server version 12.0, this metakey contains the server-relative URL of the service with the default value "/_layouts/settings.aspx" appended to the end.

<8> Section 2.2.2.3.21: FrontPage Server Extensions: Website Management Protocol version 12.0 provides the following default list of categories when a site is created:

  • Travel

  • Expense Report

  • Business

  • Competition

  • Goals/Objectives

  • Ideas

  • Miscellaneous

  • Waiting

  • VIP

  • In Process

  • Planning

  • Schedule

<9> Section 2.2.2.3.28: FrontPage 2003 and SharePoint Designer 2007 use this metakey. Windows SharePoint Services does not use this metakey.

<10> Section 2.2.2.3.56: FrontPage Server Extensions: Website Management Protocol version 12.0 sets this value to 1.

<11> Section 2.2.2.3.58: The Windows operating system client uses this metadata to avoid fetching the content of the file just to discover META tags with NAME="progid" and NAME="generator"; these are used to display icons for HTML files and to select an appropriate editor.

<12> Section 2.2.2.3.67: Windows SharePoint Services 3.0 does not return the vti_setuppath (section 2.2.2.3.67) parameter.

<13> Section 2.2.2.3.70: Due to a programming defect, if the version is at least 12.0 of the FrontPage Server Extensions: Website Management Protocol, the server does not return this metakey in the checkin document (section 3.1.5.3.6) or put document (section 3.1.5.3.25) methods. However, the server will return this metakey in the getDocsMetaInfo (section 3.1.5.3.16) and list documents (section 3.1.5.3.20) methods.

<14> Section 2.2.2.3.71: The FrontPage Server Extensions: Website Management Protocol does not have a method to set this metakey for a document. Windows SharePoint Services 3.0 sets this metakey in response to methods invoked through a SOAP-based protocol.

<15> Section 2.2.2.3.85: The default value for this metakey in FrontPage Server Extensions: Website Management Protocol version 12.0 servers is "/_layouts/1033/toolpane.aspx".

<16> Section 3.1.1.1: The FrontPage Server Extensions: Website Management Protocol version 12.0 does not allow users to turn the source control sandbox off.

<17> Section 3.1.2.1: All Windows operating system clients request a short-term checkout length of ten minutes. The clients attempt to renew the short-term checkout 10 seconds before it expires.

<18> Section 3.1.3.2.1: Windows Vista operating system does not perform this GET, and instead assumes the values shown in the example in section 3.1.3.2.1.

<19> Section 3.1.5.1: If the client does not include FrontPage in its User-Agent string, the Windows NT, Windows Server 2003 operating system, Windows Server 2008 operating system with Service Pack 2 (SP2), and Windows Server 2008 R2 operating system operating systems will respond with the HTTP Content-Type as "text/html" and present more simplistic error strings.

<20> Section 3.1.5.2: Version 12.0 of the FrontPage Server Extensions: Website Management Protocol server will treat unknown arguments as a syntax error if the method takes any parameters. For methods that take no parameters, such as server version, the FrontPage Server Extensions: Website Management Protocol server will ignore the parameters.

<21> Section 3.1.5.2: Due to a programming defect, FrontPage Server Extensions: Website Management Protocol server version 12.0 will erroneously return a badly formed response message body that is not compliant with [RFC2616] for most method calls made without authentication that result in an HTTP 401 error response.

The following is an example of this badly formed message body that is produced in this case:

  
 <html dir="ltr">
   <HEAD>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" 
      name="CharsetDefinition">
   </HEAD>
   <body ID=idErr>
     <p><H2>Access denied.</H2></p>
     <p>You do not have permission to perform this action or access
        this resource.</p>
     <!-- commentElt Access denied. -->
   </body>
 </html>
 <html>
   <head>
     <title>vermeer RPC packet</title>
   </head>
   <body>
     <p>method=open service:12.0.0.4518
     <p>status=
     <ul>
       <li>status=917556
       <li>osstatus=0
       <li>msg=You are not authorized to execute this operation.
       <li>osmsg=
     </ul>
   </body>
 </html>   
 


Note The response message body created by the FrontPage Server Extensions server software that exhibit this defect is badly formed because of the presence of two separate <HTML> sections, which MAY cause unexpected behavior in an insufficiently robust client that attempts to render or otherwise make use of the body.

All existing FrontPage Server Extensions: Website Management Protocol clients ignore the message body, if any, returned with an HTTP 401 response. Because an update or future version of the FrontPage Server Extensions: Website Management Protocol server MAY correct this defect, clients MUST NOT rely on this defective server behavior.

<22> Section 3.1.5.3: The information for these requests applies to server extensions for versions of Microsoft FrontPage 2000, Microsoft FrontPage 2002, Microsoft FrontPage 2003, and Microsoft SharePoint Designer 2007.

<23> Section 3.1.5.3.1: FrontPage Server Extensions: Website Management Protocol version 12.0 servers require this parameter to have a value of at least 4.0.2.2611 if it is sent by a client.

<24> Section 3.1.5.3.1: FrontPage Server Extensions: Website Management Protocol version 12.0 sends this parameter.

<25> Section 3.1.5.3.1: The FrontPage Server Extensions: Website Management Protocol version 12.0 ignores this parameter.

<26> Section 3.1.5.3.1: The service_name parameter is sent by some Microsoft Office clients for some methods other than create service (section 3.1.5.3.8), remove service (section 3.1.5.3.32), and rename service (section 3.1.5.3.33), but this parameter is consistently ignored when not required by Windows SharePoint Services servers.

<27> Section 3.1.5.3.2: If the version is at least SharePoint Foundation 2010, it does not implement this method.

<28> Section 3.1.5.3.3: SharePoint Foundation 2010 does not implement this method.

<29> Section 3.1.5.3.10: The FrontPage Server Extensions: Website Management Protocol version 12.0 does not have the notion of an executable folder.

<30> Section 3.1.5.3.11: Windows SharePoint Services 3.0 does not support nonexclusive checkouts.

<31> Section 3.1.5.3.13: SharePoint Foundation 2010 does not implement this method.

<32> Section 3.1.5.3.14: SharePoint Foundation 2010 does not implement this method.

<33> Section 3.1.5.3.15: SharePoint Foundation 2010 does not implement this method.

<34> Section 3.1.5.3.17: SharePoint Foundation 2010 does not implement this method.

<35> Section 3.1.5.3.18: SharePoint Foundation 2010 does not implement this method.

<36> Section 3.1.5.3.19: SharePoint Foundation 2010 does not implement this method.

<37> Section 3.1.5.3.20: The FrontPage Server Extensions: Website Management Protocol clients send listDerived=false in the request and do not request the contents of a _derived folder.

<38> Section 3.1.5.3.20: The FrontPage Server Extensions: Website Management Protocol version 5.0 and version 12.0 servers return an empty bot_list.

<39> Section 3.1.5.3.21: SharePoint Foundation 2010 does not implement this method.

<40> Section 3.1.5.3.22: SharePoint Foundation 2010 does not implement this method.

<41> Section 3.1.5.3.26: The FrontPage Server Extensions: Website Management Protocol version 12.0 does not support this behavior.

<42> Section 3.1.5.3.27: SharePoint Foundation 2010 does not implement this method.

<43> Section 3.1.5.3.28: SharePoint Foundation 2010 does not implement this method.

<44> Section 3.1.5.3.29: SharePoint Foundation 2010 does not implement this method.

<45> Section 3.1.5.3.30: SharePoint Foundation 2010 does not implement this method.

<46> Section 3.1.5.3.31: The FrontPage Server Extensions: Website Management Protocol version 12.0 does not support this behavior.

<47> Section 3.1.5.3.31: The SharePoint Designer 2007 sends an empty METADICT (section 2.2.2.2.11).

<48> Section 3.1.5.3.31: The SharePoint Designer 2007 sends an empty METADICT (section 2.2.2.2.11).

<49> Section 3.1.5.3.32: The FrontPage Server Extensions: Website Management Protocol version 5.0 can delete a site even when there are subsites present.

<50> Section 3.1.5.3.35: SharePoint Foundation 2010 does not implement this method.

<51> Section 3.1.5.3.38: In Windows SharePoint Services 3.0, source control is turned on and this method has no effect on the server.

<52> Section 3.1.5.3.38: SharePoint Foundation 2010 does not implement this method.

<53> Section 3.1.5.3.40: The FrontPage Server Extensions: Website Management Protocol version 12.0 requires that the user have a special break checkout right.