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

Possibility to use old-style calling format for s3 #7451

Closed
cyberduck opened this issue Sep 16, 2013 · 3 comments
Closed

Possibility to use old-style calling format for s3 #7451

cyberduck opened this issue Sep 16, 2013 · 3 comments
Assignees
Labels
enhancement fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

da06755 created the issue

If path value is defined in s3 connection properties this path is used as sumbdomain for server value:

server: example.com
path: mypath

request are made to mypath.example.com.

In s3 emulation for openstack swift old-style calling format is accepted, so properly handled request should look like this:

example.com/mypath

It would be great if we have possibility to choose which calling format want to use.

Openstack swift s3 documentation: http://docs.openstack.org/trunk/openstack-object-storage/admin/content/configuring-openstack-object-storage-with-s3_api.html

Boto: http://boto.readthedocs.org/en/latest/ref/s3.html#boto.s3.connection.OrdinaryCallingFormat

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This is a regression as previously we used bucket names in the request path if not connecting to s3.amazonaws.com.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In b2539d5.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Follow-up in #7967.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants