docs/src/unlock.md@bacb54502b24
docs/src/unlock.md
Thu, 21 Dec 2017 19:48:27 +0100
- author
- Mike Becker <universe@uap-core.de>
- date
- Thu, 21 Dec 2017 19:48:27 +0100
- changeset 359
- bacb54502b24
- parent 285
- 02d3e4b1245f
- permissions
- -rw-r--r--
davql: allow ANYWHERE keyword in SELECT statements
This may seem pointless, but users might want to be explicit about this and the grammar is more consistent.
This commit also adds some no-ops to the functions body of the SET parser, because some day the grammar might allow more clauses after the WHERE clause.
--- title: 'dav unlock' --- **`dav unlock [-pc] [-L <lock>] <url>`** Unlocks the specified *url* with a lock token. If no lock token is specified with the `-L` option, it read from stdin. **`-p`** disable file name and path decryption if enabled **`-c`** enable file name and path decryption **`-L <lock>`** use the specified lock token ### Example 1: unlock with lock token from stdin $ dav lock myserv/resource > locktoken $ dav unlock myserv/resource < locktoken ### Example 2: unlock with lock token from command line argument $ dav lock myserv/resource opaquelocktoken:0454905e-f2ff-45c4-a3d7-5c4e4db5ce37 $ dav unlock -L opaquelocktoken:0454905e-f2ff-45c4-a3d7-5c4e4db5ce37 myserv/resource
