-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persistent lock: cannot unshare from self #33847
Comments
GitMate.io thinks possibly related issues are #28337 (Applications cannot detect "unshare from self"), #17244 (Unshare from user must lock path to avoid recipient access), #33778 (Persistent lock timeout value is "Second-" when not specified.), and #28197 (Old chunking on new endpoint broken when using if-match header). |
|
might be related to #33885 which is fixed now. will submit a PR to reenable the test which will tell us whether it works now... |
PR here #34099 |
failed... ok, then this will need more bugfixing |
Expected behavior for now. Could reconsider in the future. Action point: adjust acceptance test |
@individual-it can you adjust the test expectation ? |
the "expected for now" related to a discussion with @DeepDiver1975 where the idea was that we are "touching" the resource anyway, even if it doesn't affect the owner. Or say the resource is locked so people should not be able to do anything with it. |
Steps
curl -u user1:test -X LOCK http://localhost/owncloud/remote.php/webdav/test -d "<?xml version='1.0' encoding='UTF-8'?><d:lockinfo xmlns:d='DAV:'> <d:lockscope><d:shared/></d:lockscope></d:lockinfo>"
Expected result
Unshare works as it doesn't affect the original folder.
Actual result
Unshare fails.
Version
Observed on #32250
In general for any locking operations, we need to consider it relative to the storage owner's storage.
If an operation would not affect the original folder like unsharing from self, we should let it through.
@DeepDiver1975 @individual-it FYI
The text was updated successfully, but these errors were encountered: