-
Notifications
You must be signed in to change notification settings - Fork 196
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
[sharing-ng] update/disable virtual space returns 500 error #7881
Labels
Comments
See also #6993 |
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
Jan 17, 2024
…them Return a 405 Status when UpdateSpace() or DeleteSpace() are not implemented in the backend for a certain type of drive (e.g. the virtual mountpoint drives created for shares). Fixes: owncloud#7881
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
Jan 17, 2024
…them Return a 405 Status when UpdateSpace() or DeleteSpace() are not implemented in the backend for a certain type of drive (e.g. the virtual mountpoint drives created for shares). Fixes: owncloud#7881
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
Jan 17, 2024
…them Return a 405 Status when UpdateSpace() or DeleteSpace() are not implemented in the backend for a certain type of drive (e.g. the virtual mountpoint drives created for shares). Fixes: owncloud#7881
ownclouders
pushed a commit
that referenced
this issue
Jan 22, 2024
…them Return a 405 Status when UpdateSpace() or DeleteSpace() are not implemented in the backend for a certain type of drive (e.g. the virtual mountpoint drives created for shares). Fixes: #7881
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Trying to send a PATCH or DELETE to a virtual space (Shares) throws an 500 error
Expected behavior
405 HTTP response
Actual behavior
HTTP 500
{"error":{"code":"generalException","innererror":{"date":"2023-12-05T09:26:13Z","request-id":"eb2eb607293d/ADjidDU61G-030279"},"message":"grpc error"}}
The text was updated successfully, but these errors were encountered: