Jeffrey Tolar 7511b6f4f1 b2: don't include the bucket name in public link file prefixes ... Including the bucket name as part of the `fileNamePrefix` passed to `b2_get_download_authorization` results in a link valid for objects that have the bucket name as part of the object path; e.g., rclone link :b2:some-bucket/some-file would result in a public link valid for the object `some-bucket/some-file` in the `some-bucket` bucket (in rclone-remote parlance, `:b2:some-bucket/some-bucket/some-file`). This will almost certainly result in a broken link. The B2 docs don't explicitly specify this behavior, but the example given for `fileNamePrefix` provides some clarification. See https://www.backblaze.com/b2/docs/b2_get_download_authorization.html.		2021-04-26 16:56:41 +01:00
..
api	b2: factor version handling into lib/version	2021-04-12 15:59:18 +01:00
b2_internal_test.go	build: fix up package paths after repo move	2019-07-28 18:47:38 +01:00
b2_test.go	build: fix up package paths after repo move	2019-07-28 18:47:38 +01:00
b2.go	b2: don't include the bucket name in public link file prefixes	2021-04-26 16:56:41 +01:00
upload.go	b2: cancel in progress multipart uploads and copies on rclone exit #4300	2020-06-25 15:22:53 +01:00