From d0560c252695ce162fb97eaf02130ffac326f033 Mon Sep 17 00:00:00 2001 From: Matthieu Gallien Date: Fri, 6 Oct 2023 09:40:50 +0200 Subject: [PATCH] lock-timeout can have a special value of 0 for infinite timeout Signed-off-by: Matthieu Gallien --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3016c383..2581bfcc 100644 --- a/README.md +++ b/README.md @@ -61,7 +61,7 @@ WebDAV returns the following additional properties if requests through a `PROPFI - `{http://nextcloud.org/ns}lock-owner-displayname`: Display name of the lock owner - `{http://nextcloud.org/ns}lock-owner-editor`: App id of an app owned lock to allow clients to suggest joining the collaborative editing session through the web or direct editing - `{http://nextcloud.org/ns}lock-time`: Timestamp of the log creation time -- `{http://nextcloud.org/ns}lock-timeout`: TTL of the lock in seconds staring from the creation time +- `{http://nextcloud.org/ns}lock-timeout`: TTL of the lock in seconds staring from the creation time. a value of 0 means the timeout is infinite. client implementations should properly handle this specific value - `{http://nextcloud.org/ns}lock-token`: Unique lock token (to be preserved on the client side while holding the lock to sent once full webdav locking is implemented) ```bash