Token Lock and Put

[Meena Vyas <me...@sun.com>]

	I guess what I collected from running this slide  is,

	Whenever I lock exclusively a resource, I get back a lockid say  <opaquelocktoken:49343697a90aeb72886f6c66cfd40233>. For this user to do a PUT, he has to send this lockid in the PUT request as a "If" header otherwise his operation will fail. 

HOWEVER ... When another user tries to do a PUT, and includes this lockid in the "If" header in the request (see request below), he succeeds. Even though he is not the person who LOCKed the resource.

	PUT /slide/files/a.html HTTP/1.0
	Authorization: Basic password-encrypted
	If: (<opaquelocktoken:49343697a90aeb72886f6c66cfd40233>)
	Content-length: 57

	<HTML>
	This WORKS!!!!  END OF DAY's WORK... MeeNA FINAL
	</htmL>

	
Is this the desired behaviour ? Or is this a bug?
Meena

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>