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
To get the indicators, web is doing 2 OCS requests to get the shares for the current and parent folders.
The problem is that the last request is done without the path filter query param, which means all the shares are returned. This is expensive and returns lots of information we already have.
Imagining we have created the tree /New folder/New folder, the last request will include it:
GET https://ocis.ocis-web.latest.owncloud.works/ocs/v1.php/apps/files_sharing/api/v1/shares?path=%2FNew%20folder%2FNew%20folder&reshares=true
I suppose what is wrong here is the ocs request without filter because that's expensive and the individual requests for specific folders might be less so (are they?).
Also, if we already rely on the webdav response for the current folder, I assume we only need to query ocs for the parent folders, but I see a request for the current one as well.
(ps: this issue was reported via chat before, just added it here for better tracking)
The text was updated successfully, but these errors were encountered:
To get the indicators, web is doing 2 OCS requests to get the shares for the current and parent folders.
The problem is that the last request is done without the path filter query param, which means all the shares are returned. This is expensive and returns lots of information we already have.
Imagining we have created the tree
/New folder/New folder
, the last request will include it:but this is redundant because we already did
I suppose what is wrong here is the ocs request without filter because that's expensive and the individual requests for specific folders might be less so (are they?).
Also, if we already rely on the webdav response for the current folder, I assume we only need to query ocs for the parent folders, but I see a request for the current one as well.
(ps: this issue was reported via chat before, just added it here for better tracking)
The text was updated successfully, but these errors were encountered: