Re: Issue #68: UNLOCK_WITHOUT_GOOD_TOKEN

OK,

to summarize (
<http://greenbytes.de/tech/webdav/draft-reschke-webdav-locking-latest.html#rfc.issue.068_UNLOCK_WITHOUT_GOOD_TOKEN>):

- errors linked to missing or bad tokens in the "lock-token" request 
header do *not* cause a 412 ("lock-token" isn't part of the headers for 
which 412-style preconditions are checked),

- clients need to be able to handle all 4xx status codes anyway,

- we define a specific precondition for missing/bad lock tokens inside 
the lock-token request header, so clients can more precisely identity 
this error condition

Jason, you may want to update your issues list accordingly.

Best regards, Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760