https://bugs.documentfoundation.org/show_bug.cgi?id=103679
--- Comment #4 from Aleksander Machniak <machn...@kolabsys.com> ---
(In reply to Tor Lillqvist from comment #3)
> I think the problem here is that the message should say something about "or
> other server error", not just disk space?
Yes, but the error is only a part of the story. Also, if you check WOPI docs
there's 413 error code specifically for "Entity too large", which is not
exactly "No disk space", but close.
Anyway, in Kolab we have such scenario:
1. User A creates a document editing session on his file and invites User B
2. User B has no permission to that file (even read-only), just have no access
to the file,
3. However, because he was invited he can join the session and edit the
document with its owner,
4. But he has no permission to the file, he can't use the Save button. So, if
he click Save and we send the PutFile request it will respond with 404 or 500,
maybe 503.
In that scenario switching to read-only mode is not what we want. User B needs
to still be able to edit the document but he needs to ask User A to save
changes they both made.
I could consider disabling the Save button for User B on the host page, but
this is not really a solution.
On the other hand if the error happens for User A, do we really want to broke
the session? No. We should warn the user and give him possibility to download
current document state or close the session.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
