-
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
Shares: server reported no etag #3353
Comments
Same with
|
Good question. This occurs when there are no shares. As soon as we have some accepted shares the etag appears. |
To be clear, I'd vote for clients to be more forgiving when there is no etag. Future implementations of storage spaces may not have an etag or an mtime. For example when accessing a tape archive. That being said a workaround on the server side is to always return an etag, either a random one or a static one, depending on what should be achieved. IN this case however, I vote for hiding the share jail when there are no shares. The ListStorageSpaces should not return the storage space of type |
IMO we cannot change the clients out there. So i vote for solution 2: only return a shares jail when there are shares. |
I'm not saying wo change all the clients to fix this problem. All I am saying is that clients should be more forgiving. A resource does not have an etag. So what? That only means clients cannot decide when to descend into a folder. I think Postel's law applies: be conservative in what you do, be liberal in what you accept from others.. Desktop and mobile and even web clients could ignore the folder and only update local metadata when the user manually descends / explores the tree. But that is a different issue and should be tracked elsewhere / at another time. |
This endpoint is backwards compatible, so folders need etags. Different story for the new spaces endpoint. Happy to discuss etag-less spaces. |
@butonic so quick solution: always have an etag. Needs fix in beta. |
@felix-schwarz @TheOneRing Is it also possible to not have a share jail when there are no shares? |
In the legacy WebDAV endpoint, the share jail is just a regular folder for the clients. So if there is no folder, there’s not a problem. |
I don't see a problem with that at the moment. It just wouldn't show up in the drive/spaces list then. |
This issue is about the legacy endpoint, which might still be used after the ocis release, as we are not able to migrate all clients. For the listing of drives, I'm pretty sure I can handle it in the client, so no need to modify anything there. |
Fixed by cs3org/reva#2664 |
Description
The error
Shares: server reported no etag
comes up as soon as I added the OCIS-traefik server on the ownCloud desktop app for manual testing.Screenshot
The text was updated successfully, but these errors were encountered: