-
Notifications
You must be signed in to change notification settings - Fork 184
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
cannot PROPFIND a received share with name when it was created, shared, deleted, recreated, reshared #7895
Comments
Just for completeness: This is not specific to sharing-ng happens also when creating the shares via ocs. (So I guess it's a bug in the sharestorageprovider) |
So basically the problem is, that we don't cleanup shares for a resource when the resource is being deleted. So when recreating (and sharing) a resource with the same name the shareprovider will return two shares when listing share by Mountpoint (which is what the sharestorageprovider needs to do for the PROPFIND). It will then just return the first share matching the mountpoint without actually checking if resource that the shared is pointing to still exist. |
This is a basically a duplicate of: #1787 🙈 |
When resolving a received shared by mountpath, make sure that the shared resource actually exists. This avoids issues with dangling shares for already delete resources using the same mountpoint. Fixes: owncloud/ocis#7895
When resolving a received shared by mountpath, make sure that the shared resource actually exists. This avoids issues with dangling shares for already delete resources using the same mountpoint. Fixes: owncloud/ocis#7895
When resolving a received shared by mountpath, make sure that the shared resource actually exists. This avoids issues with dangling shares for already delete resources using the same mountpoint. Fixes: owncloud/ocis#7895
When resolving a received shared by mountpath, make sure that the shared resource actually exists. This avoids issues with dangling shares for already delete resources using the same mountpoint. Fixes: owncloud/ocis#7895
Fix was merged as part of #8472 |
When resolving a received shared by mountpath, make sure that the shared resource actually exists. This avoids issues with dangling shares for already delete resources using the same mountpoint. Fixes: owncloud/ocis#7895 (cherry picked from commit fa2caba)
When resolving a received shared by mountpath, make sure that the shared resource actually exists. This avoids issues with dangling shares for already delete resources using the same mountpoint. Fixes: owncloud/ocis#7895 (cherry picked from commit fa2caba)
Describe the bug
In the case when a user creates a folder, shares it, then deletes it, recreates and reshares it - the receiver cannot use PROPFIND with the resource name anymore
Steps to reproduce
Expected behavior
PROPFIND should work, not depending if the folder is recreated or not
Actual behavior
PROPFIND returns
NotFound
or eveninternal Error
The PROPFIND can still be done using the fileid of the created folder, that is how web does it
Setup
Please describe how you started the server and provide a list of relevant environment variables or configuration files.
docker compose file from: https://github.com/owncloud/ocis-php-sdk/blob/main/tests/integration/compose.yaml
Additional context
I've encountered the problem when writing tests for https://github.com/owncloud/ocis-php-sdk/ the test would work one time, but break the next time
The text was updated successfully, but these errors were encountered: