implement link sharing for all remotes that support it

[breunigs]

in #2176 link sharing support was added for some remotes. This is a tracking ticket to add it for all other remotes that support it:

• Amazon Drive
• Amazon S3
• Backblaze B2 (implement link sharing for all remotes that support it #2178)
• Box
• Dropbox
• FTP
• Google Cloud Storage
• Google Drive
• HTTP - this should be trivial - just return the URL
• Hubic
• Jottacloud
• Mailru
• Mega
• Microsoft Azure Blob Storage
• OneDrive
• Openstack Swift
• OpenDrive
• pCloud
• QingStor
• S3 (s3: implement link sharing #4280)
• SFTP
• WebDAV
• Yandex Disk
• The local filesystem

checkmark means that this remote was considered. If it's strike-through, then the remote cannot support it.

EDIT 2021: added Mailru, S3, B2, removed pcloud, ACD

[theblackhole]

This might help for Openstack Swift implementation :

From what I could understand, there are two types of urls :

• urls from public containers (eg https://storage.sbg1.ovh.net/v1/AUTH_token/container-name/path/to/file.txt).
• temporary url created for a file, seems to work on private containers : https://docs.ovh.com/gb/en/public-cloud/share_an_object_via_a_temporary_url/

[ncw]

@theblackhole thanks for that. The first is probably what we want I think. Do you fancy making a pull request to implement?

[theblackhole]

@ncw Unfortunatly I don't know Golang but I may try when I got time.

[xiaolei0125]

@ncw
This might help for implement link sharing for Amazon S3 Compliant Storage Providers (AWS, Ceph, Dreamhost, IBM COS, Minio, OSS):
s3_presigned_url.go

Using presigned url for link sharing, no matter the S3 bucket is private or public.
Notice: the presigned url needs to specify the expiration time.

I have test this presigned url code with Minio and OSS(S3 Compliant), all are work fine.
The presigned url look like this:
http://x.x.x.x:9000/mybucket/my.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=CBDDBNRX5G91RTOM20K2%2F20181011%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20181011T075806Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=d1c6835e991765c63ef64560f4f6e5b1c6679610a9791f2d5db70a9bbd51a25a

Is there a way to integrate presigned url into rclone link for Amazon S3 Compliant Storage Providers ?

Below is my code for reference:
s3_presigned_url.txt

[ncw]

@xiaolei0125 would you like to send a pull request for this?

If you implement the PublicLink optional method in the s3 backend with the code above that should be it!

For the time being put a really long expires on it and we can work out how to pass the desired expiry time in a second PR.

[xiaolei0125]

@ncw Ok, I've been a bit busy recently, I may try when I got time.

[ivandeex]

I stumbled upon this ticket paging through "least recently updated, not new backend, not from ncw", preferably labeled "help wanted" (aka "we are not going to take on this anytime soon"). Such tickets are mostly rot, rusted, non-reproducible and forgotten, but not this one. It's in fact a roadmap ticket. Marking as important to not forget.

Also I'd like to propose a column in https://rclone.org/overview/#features marking backends with public links. Maybe albertony or edwardxml would be kind to tackle? (Deliberately no mentions yet to reduce noise).

cc @ncw

[ncw]

@ivandeex wrote:

I stumbled upon this ticket paging through "least recently updated, not new backend, not from ncw", preferably labeled "help wanted" (aka "we are not going to take on this anytime soon"). Such tickets are mostly rot, rusted, non-reproducible and forgotten, but not this one. It's in fact a roadmap ticket. Marking as important to not forget.

I'm not sure which backends have the PublicLink feature... A quick grep comes up with this list

$ git grep -l PublicLink | sed 's/\/.*$//' | sort | uniq

b2
box
cache
chunker
compress
crypt
drive
dropbox
jottacloud
koofr
mailru
mega
onedrive
pcloud
premiumizeme
s3
seafile
sugarsync
yandex

pcloud wasn't on the list as done. I'm going to cross off Amazon Cloud Drive as that backend is frozen since we don't have an integration test and aren't welcome anyway!

Also I'd like to propose a column in https://rclone.org/overview/#features marking backends with public links. Maybe albertony or edwardxml would be kind to tackle? (Deliberately no mentions yet to reduce noise).

That sounds like a good plan, provided we don't overload the table!

Note that you can discover what features a backend has with rclone backend features MyRemote: