Skip to content
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

Set mtime to storage after simple upload #823

Merged
merged 2 commits into from
Jun 10, 2020
Merged

Set mtime to storage after simple upload #823

merged 2 commits into from
Jun 10, 2020

Conversation

PVince81
Copy link
Contributor

  • Uploading with Webdav PUT now sets the mtime to the storage
  • Uploading with TUS POST without chunking now sets the mtime to the storage

For the chunking scenario it will be more tricky as we need to pass in the mtime through InitiateFileUpload, to be researched separately.

Part of owncloud/ocis-reva#174

Tested Webdav PUT with Phoenix by starting OCIS withREVA_FRONTEND_UPLOAD_DISABLE_TUS=true
Tested TUS POST using Phoenix PR for creation-with-upload: owncloud/web#3436
in both case, I checked that the timestamp reported by Phoenix was not "a few seconds ago"

@butonic FYI

Vincent Petry added 2 commits June 10, 2020 14:38
When using Webdav PUT, if the header X-OC-Mtime is specified, pass it on
to the storage as an arbitrary metadata.
When uploading with TUS POST using the creation-with-upload extension
without chunking, apply the mtime to the storage.
@labkode labkode merged commit 10a1ed2 into cs3org:master Jun 10, 2020
C0rby pushed a commit to owncloud/reva that referenced this pull request Jun 30, 2020
* Set mtime during upload on direct PUT

When using Webdav PUT, if the header X-OC-Mtime is specified, pass it on
to the storage as an arbitrary metadata.

* Set mtime for TUS direct single shot uploads

When uploading with TUS POST using the creation-with-upload extension
without chunking, apply the mtime to the storage.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants