The following sections list the changes in reva 1.4.0 relevant to reva users. The changes are ordered by importance.
When trying to list shares for a not existing file or folder the ocs sharing implementation no longer responds with the wrong status code and broken xml.
https://github.com/cs3org/reva/pull/1316
We now filter deleted and unshared entries from the response when listing the shares folder of a user.
https://github.com/cs3org/reva/pull/1274
We now treat E2BIG, EACCES as a permission error, which occur, eg. when acl checks fail and return a permission denied error.
https://github.com/cs3org/reva/pull/1269
The publicfile handler needs to check the response status code to return proper not pound and permission errors in the webdav api.
https://github.com/cs3org/reva/pull/1297
File descriptors on the ocdav service, especially on the put handler was leaking http connections. This PR addresses this.
https://github.com/cs3org/reva/pull/1260
In the PUT handler for chunked uploads in ocdav, we store the individual chunks in temporary file but do not write the assembled file to storage. This PR fixes that.
https://github.com/cs3org/reva/pull/1253
We now use a new synctime timestamp instead of trying to read the mtime to avoid race conditions when the stat request happens too quickly.
https://github.com/owncloud/product/issues/249 https://github.com/cs3org/reva/pull/1264
When checking permissions we were always checking the leaf instead of using the current node while iterating over path segments.
https://github.com/cs3org/reva/pull/1255
We no longer set the propagation flag on a file because it is only evaluated for folders anyway.
https://github.com/cs3org/reva/pull/1265
The OCS API now properly filters share with me requests by path and by share status (pending, accepted, rejected, all)
https://github.com/owncloud/ocis-reva/issues/260 https://github.com/owncloud/ocis-reva/issues/311 https://github.com/cs3org/reva/pull/1301
We now handle cases where the grpc connection failed correctly by no longer trying to access the response status.
https://github.com/cs3org/reva/pull/1317
When executing a propfind to a resource owned by another user the service would respond with a HTTP 403. In ownCloud 10 the response was HTTP 207. This change sets the response code to HTTP 207 to stay backwards compatible.
https://github.com/cs3org/reva/pull/1259
The method ReadNode in the ocis storage didn’t return the error type NotFound when a file was not found.
https://github.com/cs3org/reva/pull/1294
When a share was updated the share information in the share manager was updated but the grants set by the storage provider were not.
https://github.com/cs3org/reva/pull/1258
For health monitoring of all mesh sites, we need a special user account that is present on every site. This PR adds such a user to each users-*.json file so that every site will have the same test user credentials.
https://github.com/cs3org/reva/pull/1257
Applications served by the WOPI bridge (CodiMD for the time being) require an extra redirection as the WOPI bridge itself behaves like a user app. This change returns to the client the redirected URL from the WOPI bridge, which is the real application URL.
https://github.com/cs3org/reva/pull/1234
To create shares with user groups, the functionality for searching for these based on a pattern is needed. This PR adds that.
https://github.com/cs3org/reva/pull/1239
A Reva SDK has been added to make working with a remote Reva instance much easier by offering a high-level API that hides all the underlying details of the CS3API.
https://github.com/cs3org/reva/pull/1280
The grpc transfer service and cli for it.
https://github.com/cs3org/reva/pull/1237
This PR adds an SQL driver for the shares manager which expects a schema equivalent to the one used in production for CERNBox.
https://github.com/cs3org/reva/pull/1224
Previously, we were implementing the tus client logic in the ocdav service, leading to restricting the whole of tus logic to the internal services. This PR refactors that workflow to accept incoming requests following the tus protocol while using simpler transmission internally.
https://github.com/cs3org/reva/pull/1285 https://github.com/cs3org/reva/pull/1314
The new mimetype is associated with the .zmd
file extension. The corresponding
configuration is associated with the storageprovider.
https://github.com/cs3org/reva/pull/1233 https://github.com/cs3org/reva/pull/1284