[Cyberduck-trac] [Cyberduck] #7967: Preference to use path-style request URIs

Cyberduck trac at trac.cyberduck.io
Tue Nov 11 18:20:20 UTC 2014

#7967: Preference to use path-style request URIs
 Reporter:  scytacki     |         Owner:  dkocher
     Type:  enhancement  |        Status:  closed
 Priority:  low          |     Milestone:
Component:  s3           |       Version:  4.4.4
 Severity:  normal       |    Resolution:  fixed
 Keywords:               |  Architecture:
 Platform:               |

Comment (by eric herot):

 I would like to suggest that this be re-opened.  The 301 Redirect issue
 mentioned above is a strange but valid behavior considering that regions
 in S3 are essentially like completely disparate services and a bucket in
 us-east-1 has no relation to (or knowledge of) a bucket in us-west-1.

 In other words, the above 301 should probably just throw an "object not
 found" error, and the "path-style" API request method should be the
 default, with the understanding that the user must specify the correct AWS
 region in the connection profile.

 The current behavior of just expecting that S3 users with dots in their
 bucket names (which is a totally normal and supported way to use S3) are
 just going to have to put up with certificate errors all of the time is,
 frankly, irresponsible programming. It contributes to desensitization
 towards certificate errors, which is already a pernicious problem in our

 If you really don't want to make this behavior the default, could we at
 least get a "path style" checkbox on the connection profile screen?

Ticket URL: <https://trac.cyberduck.io/ticket/7967#comment:6>
Cyberduck <http://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows

More information about the Cyberduck-trac mailing list