Problem with cond_put_corrupt_token test

[Tobias Schlitt]

Hi John,

On 11/08/2008 08:04 PM John Meissen wrote:
> It's perhaps a bit unfortunate that they overloaded the "If:" header 
> this way, because it can lead to some confusion.

> There are two separate conditions that must be satisified, both
> involving the "If:" header.

> The first is the evaluation of the header itself. This determines
> whether the operation proceeds at all and is independent of whether
> or not the resource itself is actually locked. This is simply a true/false
> test. This is a global test that applies to any method, even those
> which are otherwise unaffected by locks.

> The second is whether the token for a locked resource is included in
> the "If:" header. So once the request passes the "If:" evaluation it
> still has to determine that the requested resource is locked and
> whether the token is included in the "If:" header.

> So yes, it should evaluate the condition to true, but should then
> fail because the correct token for the lock isn't in the header.

Ah, that explaination makes it much clearer to me.

Thanks a lot!
Toby
-- 
Mit freundlichen Grüßen / Med vennlig hilsen / With kind regards

Tobias Schlitt (GPG: 0xC462BC14) eZ Components Developer

ts at ez.no | eZ Systems AS | ez.no

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : http://lists.manyfish.co.uk/pipermail/litmus/attachments/20081108/062fe4d8/attachment-0006.bin