Problem with cond_put_corrupt_token test

[Tobias Schlitt]

Hi!

I'm currently working in my servers class 2 compliance. The test case
"cond_put_corrupt_token" looks broken to me. It fails with the message
"(conditional PUT with invalid lock-token should fail: 201 Created)".

I examined the If header, which looks like this:

If: (<opaquelocktoken:bed586e3-1876-3f16-b0c9-bccbd0c53947x>) (Not
<DAV:no-lock>)

The first condition is the correct lock token, appended by an 'x' and
therefore a broken lock token. However, the second condition is negated,
therefore the condition list is overall evaluated to TRUE.

The test case basically reflects the example from RFC4918 section 10.4.8
(Example - Causing a Condition to Always Evaluate to True).

Am I misslead or is the test case broken?

TIA for any hint,
cheers,
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/98c672f7/attachment-0006.bin