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

Rclone third-party copy push #3491

Merged
merged 9 commits into from
Dec 2, 2022
Merged

Rclone third-party copy push #3491

merged 9 commits into from
Dec 2, 2022

Conversation

redblom
Copy link
Contributor

@redblom redblom commented Nov 24, 2022

Rclone supports third-party copy push (as per WebDAV COPY specification).
For this to work with the OCM share flow (datatx type share) rclone must pass the tokens for both source and destination accounts with the WebDAV COPY request. The source token will be passed in the authorization header of the COPY request. The destination token will be passed as the userinfo part of the Destination header URI.
The rclone WebDAV COPY request to the source endpoint:

COPY https://reva-src/remote.php/webdav/path-to-file/file.txt
  Authorization: Bearer src-access-token
  Destination: https://dst-access-token@reva-dst/remote.php/webdav/path-to/file.txt

The webdav service at the source end will discover the userinfo part in the Destination URI and use that in the authorization header of the tpc push request.

@update-docs
Copy link

update-docs bot commented Nov 24, 2022

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

@redblom redblom changed the title [WIP] Rclone third-party copy push Rclone third-party copy push Nov 30, 2022
@gmgigi96 gmgigi96 merged commit 396dd74 into cs3org:master Dec 2, 2022
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.

None yet

3 participants