From: Olivier Goffart <ogoffart@woboq.com>
Date: Tue, 9 Oct 2018 07:20:15 +0000 (+0200)
Subject: Upload: Do not error out if the server do not send the X-OC-MTime: accepted header
X-Git-Tag: archive/raspbian/3.16.7-1_deb13u1+rpi1~1^2~12^2~21^2~468^2~472
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=18f6e346b8c3ad34e9a49f526d3a122553ce1bae;p=nextcloud-desktop.git

Upload: Do not error out if the server do not send the X-OC-MTime: accepted header

If the server does not set the mtime, it is not a big problem for the
synchronisation.

The test was used before so we could do a PROPPATCH for server that did not
support this header. But now that all server supports that we don't need to
to the check. (We do not do the PROPPATCH since we got rid of the neon
dependency)

Apparently, it may happen that some backend don't support setting mtime
and this can lead to this error.

https://github.com/owncloud/client/issues/6797
---

diff --git a/src/libsync/propagateuploadv1.cpp b/src/libsync/propagateuploadv1.cpp
index e28a7be62..c305d8f32 100644
--- a/src/libsync/propagateuploadv1.cpp
+++ b/src/libsync/propagateuploadv1.cpp
@@ -313,8 +313,6 @@ void PropagateUploadFileV1::slotPutFinished()
         // Normally Owncloud 6 always puts X-OC-MTime
         qCWarning(lcPropagateUpload) << "Server does not support X-OC-MTime" << job->reply()->rawHeader("X-OC-MTime");
         // Well, the mtime was not set
-        done(SyncFileItem::SoftError, "Server does not support X-OC-MTime");
-        return;
     }
 
     finalize();