Read the Header OC-Perm for the remote permissions on TUS.

With this the client will save a subsequent PROPFIND request
after a TUS upload. It requires that the server sends the
OC-Perm header. oCIS will do that.

1 files changed, 9 insertions, 1 deletions

diff --git a/src/libsync/propagateuploadtus.cpp b/src/libsync/propagateuploadtus.cpp
index aad0de582..f57c35d37 100644
--- a/src/libsync/propagateuploadtus.cpp
+++ b/src/libsync/propagateuploadtus.cpp
@@ -229,10 +229,18 @@ void PropagateUploadFileTUS::slotChunkFinished()
         startNextChunk();
         return;
     }
+
+    // ==== handling when the upload is finished:
     const QByteArray etag = getEtagFromReply(job->reply());
+    const QByteArray remPerms = job->reply()->rawHeader("OC-Perm");
+    if (!remPerms.isEmpty()) {
+        _item->_remotePerm = RemotePermissions::fromServerString(QString::fromUtf8(remPerms));
+    }
 
-    _finished = !etag.isEmpty();
+    _finished = !(etag.isEmpty() || _item->_remotePerm.isNull());
     if (!_finished) {
+        // Either the ETag or the remote Permissions were not in the headers of the reply.
+        // Start a PROPFIND to fetch these data from the server.
         auto check = new PropfindJob(propagator()->account(), propagator()->fullRemotePath(_item->_file));
         _jobs.append(check);
         check->setProperties({ "http://owncloud.org/ns:fileid", "http://owncloud.org/ns:permissions", "getetag" });