-
Notifications
You must be signed in to change notification settings - Fork 668
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
Incorrect handling of unlimited/unknown disk quota #3940
Comments
To get quota information, the client does this kind of request:
which would typically be answered like this:
Where would the -1, -2 or -3 show up? As a quota value? |
<?xml version="1.0" encoding="utf-8"?>
<d:multistatus xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns" xmlns:oc="http://owncloud.org/ns">
<d:response>
<d:href>/owncloud/remote.php/webdav/</d:href>
<d:propstat>
<d:prop>
<d:quota-available-bytes>-3</d:quota-available-bytes>
<d:quota-used-bytes>15192979931</d:quota-used-bytes>
</d:prop>
<d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
</d:response>
</d:multistatus> |
ogoffart
added a commit
that referenced
this issue
Oct 29, 2015
Don't show a progress bar if there is an unkown or unlimited total
I tested by hardcoding the value in the code. I don't know how to ge the server to actually return these special values |
Now works as expected, thanks |
dragotin
added a commit
to dragotin/owncloud_for_filelink
that referenced
this issue
Feb 2, 2017
Only check if the quota is a positive number, otherwise quota is either unknown or unlimited. See owncloud/client#3940 for details.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some external storage backend either don't provide quota information or provide unlimited storage.
When quota information is requested for such a storage oC will return
-2
for unknown free space and-3
for unlimited free space (-1
is for not computed).The sync client does't handle these values and shows the quota being full in the user interface
The text was updated successfully, but these errors were encountered: