It appears that some time in the last few months prior to 6.9.4, rackspace:// was treated the same as rackspace:/ but this is no longer the case the the URI cannot be specified with two slashes. If it is the item is treated as server address which is non-sensical for the rackspace protocol.
To resolve this bug the help should have the extra slash removed to become:
Ok, looks to be a duplicate of another bug. I saw it on 6.9.4 but is fixed in 7.0.2 (OSX via brew.sh)
$ duck --help
Usage:duck [options...]
...
Windows Azure Blob Storage azure:(//<hostname>)/<container>/<key>
Backblaze B2 Cloud Storage b2:/<container>/<key>
Google Cloud Storage gs:/<container>/<key>
Amazon S3 s3:(//<hostname>)/<container>/<key>
Rackspace Cloud Files (US) rackspace:/<container>/<key>
Swift (OpenStack Object Storage) swift://<hostname>/<container>/<key>
DRACOON (OAuth) dracoon:(//<hostname>)/<folder>/<file>
...
open a ticket at https://trac.cyberduck.io/newticket?version=7.0.2.
Not registered. Purchase a donation key to support the development of this software.
cyberduck commentedAug 2, 2019
The CLI help lists the Rackspace Cloud files protocol as
$ duck --help
Usage:duck [options...]
...
Default protocols
...
Rackspace Cloud Files (US) rackspace:///
...
However the documentation at https://trac.cyberduck.io/wiki/help/en/howto/cli#URI lists the protocol as
rackspace:// (absolute)
rackspace:/ (relative)
It appears that some time in the last few months prior to 6.9.4, rackspace:// was treated the same as rackspace:/ but this is no longer the case the the URI cannot be specified with two slashes. If it is the item is treated as server address which is non-sensical for the rackspace protocol.
To resolve this bug the help should have the extra slash removed to become:
$ duck --help
Usage:duck [options...]
...
Default protocols
...
Rackspace Cloud Files (US) rackspace://
...
I have examined the source and each protocol is enumerated from lines 59-71 of https://github.com/iterate-ch/cyberduck/blob/master/cli/src/main/java/ch/cyberduck/cli/TerminalHelpPrinter.java
The text was updated successfully, but these errors were encountered: