-
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
500 status code on update share #2011
Comments
In step 6, when user
However, now when user Brian deletes his last share as: The response is:
But the share to user |
Now, the behaviour is different when using ocs-api-version 1.
However, with status code |
Investigation of: #1999 |
Duplicate of #1950 ? If yes, please close. |
NO. This is different issue. |
Since this is 3 years old I consider it either fixed or not relevant enough to be fixed. Closing. |
The issue number is no longer mentioned in expected-failures, so it must have been fixed. |
Describe the bug
In ocis, when a user tries to update the last created share using the int value of the share_id, the status code is 500 when ocs_api_version 2 is used.
Steps to reproduce
Steps to reproduce the behavior:
Alice
,Brian
andCarol
Alice
, create a folder/TMP
and share the folder with userBrian
Brian
, get all the shares and accept the share/TMP
as:Brian
, share folderShares/TMP
with userCarol
Carol
, get all the shares and accept the shareShares/TMP
asAlice
, get all the shares and update the last share as:Expected behavior
The share should be updated with the integer value as with ocs_api_version 1.
Actual behavior
While using the integer value of the share_id to update the share, the server responds with 500 internal server error.
WIth the actual share_id used, the share is actually updated, but after the share permisson has been updated, the share receiver
Brian
gets 500 server error when the share toCarol
is tried to be deleted.In short, the behavior on
Ocs_api_version 1
andOcs_api_version 2
are different.The text was updated successfully, but these errors were encountered: