Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of Bennett.Tony@con-way.com
 designates 63.230.177.41 as permitted sender)
From: "Bennett, Tony" <Bennett.Tony@con-way.com>
To: "'users@httpd.apache.org'" <users@httpd.apache.org>
Date: Wed, 26 Sep 2012 13:53:52 -0700
Thread-Topic: Why does a DELETE transaction check for locks on Parent
 Collection
Thread-Index: Ac2cKQmQ07u11sIZTqaU97eFHkmkbw==
Message-ID: 
 <9E085D377965634187A85638358AE61101C93C044B@DCXPRCL017.cnf.prod.cnf.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [users@httpd] Why does a DELETE transaction check for locks on Parent
 Collection

Environment:=09
	Version:	    2.2.16
	Platform OS:    AIX 6.1
	Configuration:  WebDav enabled
	Client:	    Windows 7 "Mapped Network Drive"

Here is the interaction:

Client  sends a PUT
Server  responds with a 200
Client  sends a LOCK request
Server  responds with a 200 and this header is in the response:
		Lock-Token: <opaquelocktoken:f86e1996-0726-11e2-b22c-c30f656528a6>
Client  sends a DELETE and includes this header in the request:
		If: (<opaquelocktoken:f86e1996-0726-11e2-b22c-c30f656528a6>)
Server  responds with a 424 Failed Dependency and includes this text in its=
 response body:
       <?xml version=3D"1.0" encoding=3D"utf-8"?>
       <D:multistatus xmlns:D=3D"DAV:">
       <D:response>
       <D:href>/TEST_DIR</D:href>
       <D:status>HTTP/1.1 412 Precondition Failed</D:status>
       <D:responsedescription>A validation error has occurred on the parent=
 resource,=20
       preventing the operation on the resource specified by the Request-UR=
I. The error was:=20
       The precondition(s) specified by the "If:" header did not match this=
 resource. At=20
       least one failure is because: a State-token was supplied, but it was=
 not found in the=20
       locks on this resource.</D:responsedescription>
       </D:response>
       </D:multistatus>

Here is a subset of the Apache Error Log:
      Could not DELETE /TEST_DIR/~$EXCEL_File.xlsx due to a failed precondi=
tion (e.g. locks).  [424, #0]
     (11)Resource temporarily unavailable: An error occurred on another res=
ource, preventing the requested operation on this resource.  [424, #0]

I tried locking/deleting with cadaver, which worked.... it had a slightly d=
ifferent "If" header:
     If: <http://dmsa.con-way.com/TEST_DIR/~%24EXCEL_File.xlsx> (<opaqueloc=
ktoken:fec89268-081a-11e2-a1d7-c30f65659e0a>)

My question is why did Apache check for the "opaquetoken" against the paren=
t collection when the request came from Win7...???

I can't find a requirement to do so in the standard (RFC2518 or RFC4918).

NOTE:  I tried locking/deleting with cadaver, which worked.... it had a sli=
ghtly different "If" header:
     If: <http://dmsa.con-way.com/TEST_DIR/~%24EXCEL_File.xlsx> (<opaqueloc=
ktoken:fec89268-081a-11e2-a1d7-c30f65659e0a>)

Any insight would be helpful.

-tony


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org