Open individual-it opened 5 years ago
not critical for the release I'd say, but should be fixed right after.
I suspect that Sabre parses the part behind "opaquelocktoken:" and somehow evaluates to null instead of failing directly
GitMate.io thinks the contributor most likely able to help you is @ownclouders.
Possibly related issues are https://github.com/owncloud/core/pull/34268 (Hide lock token in public webdav responses), https://github.com/owncloud/core/pull/34270 ([stable10] Hide lock token in public webdav responses), https://github.com/owncloud/core/pull/30580 (Test unlock on exception during scanning), https://github.com/owncloud/core/issues/33479 (moving files in public folder is not possible), and https://github.com/owncloud/core/issues/29554 (overwriting a file with a folder and a folder with a file needs better error reporting).
not critical => backlog
Steps to reproduce
curl -u $LINKTOKEN: -X UNLOCK http://localhost/owncloud-core/public.php/webdav/test -H "Lock-Token: opaquelocktoken:"
Expected behaviour
error that the opaquelocktoken is not valid
Actual behaviour
Logs
ownCloud log (data/owncloud.log)
CC @PVince81 @davitol