You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When doing a PROPFIND on a public space, the response contains a dav property public-link-permission to indicate the permissions for this link. However, these permissions are being represented via permission bits, which is the old (deprecated) way of the OCS API.
Web needs this information to distinguish between the link types view and uploadOnly, since these can't be distinguished solely by the webdav permissions.
Steps to reproduce
Create a public link for a folder
Do a PROPFIND to list the resources for this folder (e.g. https://host.docker.internal:9200/remote.php/dav/public-files/CIlnOrnDLxMmPHx)
Check the server response for the first resource (= the share itself)
Expected behavior
There is a dav property that represents the link's type, since that's the graph property representing the permissions.
public-link-permission is the actual behaviour. The new property should reflect the link's type, so I'd name it public-link-type. It should be a simple string representing the type, e.g. view.
Describe the bug
When doing a
PROPFIND
on a public space, the response contains a dav propertypublic-link-permission
to indicate the permissions for this link. However, these permissions are being represented via permission bits, which is the old (deprecated) way of the OCS API.Web needs this information to distinguish between the link types
view
anduploadOnly
, since these can't be distinguished solely by the webdav permissions.Steps to reproduce
PROPFIND
to list the resources for this folder (e.g.https://host.docker.internal:9200/remote.php/dav/public-files/CIlnOrnDLxMmPHx
)Expected behavior
There is a dav property that represents the link's
type
, since that's the graph property representing the permissions.Actual behavior
The is a dav property
public-link-permission
.cc @rhafer
The text was updated successfully, but these errors were encountered: