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
While a user tries to get the info of the share using the share id, the ocs status message is Only GET, POST and PUT are allowed if that user is not allowed to access the share.
Steps to reproduce
Create users: Alice and Brian and Carol
User Alice created and shared file toShareWithBrian.txt with the user "Brian"
As user Carol, send a HTTP GET request to the OCS API endpoint /ocs/v2.php/apps/files_sharing/api/v1/shares/<LAST_SHARE_ID>
Expected behavior
The response should be something like that in OC10 in which the ocs status code is 404
Actual behavior (In OCIS)
As user Carol, when HTTP GET request is sent for /ocs/v2.php/apps/files_sharing/api/v1/shares/501b093e-39b9-431c-9234-c343ae215903 where 501b093e-39b9-431c-9234-c343ae215903 is the share id for the share of file toShareWithBrian.txt, I get the following response
<?xml version="1.0" encoding="UTF-8"?>
<ocs>
<meta>
<status>error</status>
<statuscode>400</statuscode>
<message>Only GET, POST and PUT are allowed</message>
</meta>
</ocs>
While a user tries to get the info of the share using the share id, the ocs status message is
Only GET, POST and PUT are allowed
if that user is not allowed to access the share.Steps to reproduce
Alice
andBrian
andCarol
Alice
created and shared filetoShareWithBrian.txt
with the user "Brian"Carol
, send a HTTP GET request to the OCS API endpoint/ocs/v2.php/apps/files_sharing/api/v1/shares/<LAST_SHARE_ID>
Expected behavior
The response should be something like that in OC10 in which the ocs status code is 404
Actual behavior (In OCIS)
As user
Carol
, when HTTP GET request is sent for/ocs/v2.php/apps/files_sharing/api/v1/shares/501b093e-39b9-431c-9234-c343ae215903
where501b093e-39b9-431c-9234-c343ae215903
is theshare id
for the share of filetoShareWithBrian.txt
, I get the following responseIn OC10
The text was updated successfully, but these errors were encountered: