You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is your current rclone version (output from rclone version)?
rclone v1.65.1
os/version: darwin 14.4.1 (64 bit)
os/kernel: 23.4.0 (x86_64)
os/type: darwin
os/arch: amd64
go/version: go1.21.5
go/linking: dynamic
go/tags: cmount
What problem are you are trying to solve?
Currently, when setting vendor to "nextcloud", rclone will MKCOL a temporary folder using the MD5 hash of the file path, prefixed with "rclone-chunked-upload-". While this works fine for Nextcloud, other implementations may not be able to take advantage of the chunking feature when the original file size is not know.
My use case is to be able to use rclone against storage systems that support chunked upload through API, but not WebDAV. That can be possible by writing a proxy on top of the API. However, some API requires knowing the file size beforehand before accepting chunks.
Alternatively, we can append it to the name of the temporary upload folder, i.e. rclone-chunked-upload-:md5-:size. This way uploading to NextCloud still works normally.
Or we can do both.
I don't think it's a big change, and it's not breaking anything. I'd be happy to submit a PR if it's acceptable.
How to use GitHub
Please use the 👍 reaction to show that you are affected by the same issue.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
The text was updated successfully, but these errors were encountered:
What is your current rclone version (output from rclone version)?
rclone v1.65.1
What problem are you are trying to solve?
Currently, when setting
vendor
to "nextcloud",rclone
willMKCOL
a temporary folder using the MD5 hash of the file path, prefixed with "rclone-chunked-upload-". While this works fine for Nextcloud, other implementations may not be able to take advantage of the chunking feature when the original file size is not know.My use case is to be able to use rclone against storage systems that support chunked upload through API, but not WebDAV. That can be possible by writing a proxy on top of the API. However, some API requires knowing the file size beforehand before accepting chunks.
Example usage:
How do you think rclone should be changed to solve that?
Include the file size somewhere. One way is to use "Content-Range" header like Google Cloud Storage (https://cloud.google.com/storage/docs/performing-resumable-uploads#chunked-upload). However, that does not help when file size is needed in advance of the
PUT
.Alternatively, we can append it to the name of the temporary upload folder, i.e.
rclone-chunked-upload-:md5-:size
. This way uploading to NextCloud still works normally.Or we can do both.
I don't think it's a big change, and it's not breaking anything. I'd be happy to submit a PR if it's acceptable.
How to use GitHub
The text was updated successfully, but these errors were encountered: