The following sections list the changes in reva 1.6.0 relevant to reva users. The changes are ordered by importance.
We now use the same percent encoding for URLs in WebDAV href properties as ownCloud 10.
https://github.com/owncloud/ocis/issues/1120 https://github.com/owncloud/ocis/issues/1296 https://github.com/owncloud/ocis/issues/1307 https://github.com/cs3org/reva/pull/1425 https://github.com/cs3org/reva/pull/1472
We now correctly render oc:permissions
on the root collection of a publicly shared folder
when it has more than read permissions.
https://github.com/cs3org/reva/pull/1461
This update fixes a bug in Mentix that caused some (non-critical) values to be lost during data cloning that happens internally.
https://github.com/cs3org/reva/pull/1457
This wasn’t possible before if the directory was not empty
https://github.com/cs3org/reva/pull/1429
Previously the status code was gathered from the wrong response.
https://github.com/cs3org/reva/pull/1408
Recipients can now be distinguished by their email, which is rendered as additional info in the ocs api for share and file owners as well as share recipients.
https://github.com/owncloud/ocis/issues/1190 https://github.com/cs3org/reva/pull/1451
We categorized all expected failures into File (Basic file management like up and download, move, copy, properties, trash, versions and chunking), Sync (Synchronization features like etag propagation, setting mtime and locking files), Share (File and sync features in a shared scenario), User management (User and group management features) and Other (API, search, favorites, config, capabilities, not existing endpoints, CORS and others). The Review and fix the tests that have sharing step to work with ocis reference has been removed, as we now have the sharing category
https://github.com/owncloud/core/issues/38006 https://github.com/cs3org/reva/pull/1424
https://github.com/cs3org/reva/pull/1434
We now support checksums on file uploads and PROPFIND results. On uploads, the ocdav service
now forwards the OC-Checksum
(and the similar TUS Upload-Checksum
) header to the storage
provider. We added an internal http status code that allows storage drivers to return checksum
errors. On PROPFINDs, ocdav now renders the <oc:checksum>
header in a bug compatible way for
oc10 backward compatibility with existing clients. Finally, GET and HEAD requests now return
the OC-Checksum
header.
https://github.com/owncloud/ocis/issues/1291 https://github.com/owncloud/ocis/issues/1316 https://github.com/cs3org/reva/pull/1400 https://github.com/owncloud/core/pull/38304
https://github.com/cs3org/reva/pull/1431
The OCDAV propfind response previously hardcoded the TUS headers due to which clients such as phoenix used the TUS protocol for uploads, which EOS doesn’t support. Now we pass this property as an opaque entry in the containers metadata.
https://github.com/cs3org/reva/pull/1415
https://github.com/cs3org/reva/pull/1402
https://github.com/cs3org/reva/pull/1477
We cache the home directory and shares folder etags as calculating these is an expensive process. But if these directories were updated after the previously calculated etag was cached, we can ignore this calculation and directly return the new one.
https://github.com/cs3org/reva/pull/1416
https://github.com/cs3org/reva/pull/1478
https://github.com/cs3org/reva/pull/1453
Recently, there was a separation of concerns with regard to users and groups in CS3APIs. This PR adds the required stubs and drivers for the group manager.
https://github.com/cs3org/cs3apis/pull/99 https://github.com/cs3org/cs3apis/pull/102 https://github.com/cs3org/reva/pull/1358
The share passwords were only base64 encoded. Added hashing using bcrypt with configurable hash cost.
https://github.com/cs3org/reva/pull/1462
https://github.com/cs3org/reva/pull/1464
As a developer creating/maintaining a storage driver I want to be able to validate the atomicity of all my storage driver operations. * Test for: Start 2 uploads, pause the first one, let the second one finish first, resume the first one at some point in time. Both uploads should finish. Needs to result in 2 versions, last finished is the most recent version. * Test for: Start 2 MKCOL requests with the same path, one needs to fail.
https://github.com/cs3org/reva/pull/1430
https://github.com/cs3org/reva/pull/1456
We added a new storage driver (s3ng) which stores the file metadata on a local filesystem (reusing the decomposed filesystem of the ocis driver) and the actual content as blobs in any s3-compatible blobstore.
https://github.com/cs3org/reva/pull/1429
https://github.com/cs3org/reva/pull/1467