none
[MS-WDV]: WebDAV Client Extensions lock and COPY clarification needed RRS feed

  • Question

  • [MS-WDV]: Web Distributed Authoring and Versioning (WebDAV) Protocol: Client 
    Extensions. 

    In section 2.2.2 the specification introduces a new HTTP header "Translate". 
    With the "Translate: F" header the WebDAV server is supposed to return the 
    script source code rather than the dynamically generated content. 

    Section 3.2.5.2 requires that the server honors the locks in un-translated 
    requests. However it is not clear how the locks on the script source files 
    interact with the locks on the dynamic content they are generating. E.g. if 
    someone sets a lock on the ASP source file will this also lock the access to 
    the content generated by that ASP? 

    It is also not clear how the "translate: F" header should be handled in the 
    COPY command: is the source of the copy un-translated, or the destination or 
    the both? 
    Monday, June 9, 2008 8:37 PM

Answers

  •  

    Hi,

     

    We’ve concluded our investigation and would like to share with you some conceptual clarification that we are sure will help you interpret the document a little better.

     

    In section 3.2.5.2, the text states:

     

    The WebDAV server MUST honor lock headers that are sent on GET, POST, and PUT requests that are sent by using the Translate: F header if it advertises this functionality with X-MSDAVEXT: 1 in its OPTIONS response. It MAY honor these headers on requests that are not sent with Translate: F or on other methods. It SHOULD NOT send or honor these headers if it does not advertise this functionality with the X-MSDAVEXT: 1 OPTIONS response header.

     

    I’ve highlighted the expression “honor lock headers” because we believe this is where your question comes from.

     

    When we say lock headers we mean that the header will be honored in order to alter the status of the lock.

     

    Now, as the locks (per definition of the RFC) are write locks, the file will be served no matter if it’s locked or not.

     

    With regards of the COPY verb, the header is ignored in the COPY verb and this is stated in the following extract from section 2.2.2 Translate Header :

     

     

     

    This header MUST be supported on the GET verb and MAY be supported on other verbs.<9>

     

     

    <9> Section 2.2.2: This header is issued by the WebDAV client in Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. The WebDAV server ISAPI extension in Internet Information Services supports this header on all commands; however, Windows SharePoint Services 2.0 and Windows SharePoint Services 3.0 support this header on GET, POST, and HEAD commands.

     

    I hope this helps clarify your questions.

     

    Thanks and regards,

     

    SEBASTIAN CANEVARI


    SEBASTIAN CANEVARI - MSFT SEE Protocol Documentation Team
    • Proposed as answer by Sebastian Canevari Monday, August 11, 2008 9:20 PM
    • Marked as answer by KeithHa Wednesday, August 13, 2008 11:19 PM
    Monday, August 4, 2008 4:43 PM

All replies

  •  

    Thank you for posting the question regarding WebDAV client extension.  We will review your question and update the forum once our investigation is complet.
    Tuesday, June 10, 2008 4:53 PM
  •  

    Hi,

     

    We’ve concluded our investigation and would like to share with you some conceptual clarification that we are sure will help you interpret the document a little better.

     

    In section 3.2.5.2, the text states:

     

    The WebDAV server MUST honor lock headers that are sent on GET, POST, and PUT requests that are sent by using the Translate: F header if it advertises this functionality with X-MSDAVEXT: 1 in its OPTIONS response. It MAY honor these headers on requests that are not sent with Translate: F or on other methods. It SHOULD NOT send or honor these headers if it does not advertise this functionality with the X-MSDAVEXT: 1 OPTIONS response header.

     

    I’ve highlighted the expression “honor lock headers” because we believe this is where your question comes from.

     

    When we say lock headers we mean that the header will be honored in order to alter the status of the lock.

     

    Now, as the locks (per definition of the RFC) are write locks, the file will be served no matter if it’s locked or not.

     

    With regards of the COPY verb, the header is ignored in the COPY verb and this is stated in the following extract from section 2.2.2 Translate Header :

     

     

     

    This header MUST be supported on the GET verb and MAY be supported on other verbs.<9>

     

     

    <9> Section 2.2.2: This header is issued by the WebDAV client in Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. The WebDAV server ISAPI extension in Internet Information Services supports this header on all commands; however, Windows SharePoint Services 2.0 and Windows SharePoint Services 3.0 support this header on GET, POST, and HEAD commands.

     

    I hope this helps clarify your questions.

     

    Thanks and regards,

     

    SEBASTIAN CANEVARI


    SEBASTIAN CANEVARI - MSFT SEE Protocol Documentation Team
    • Proposed as answer by Sebastian Canevari Monday, August 11, 2008 9:20 PM
    • Marked as answer by KeithHa Wednesday, August 13, 2008 11:19 PM
    Monday, August 4, 2008 4:43 PM