We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
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
The text was updated successfully, but these errors were encountered:
@dkocher commented
This is a regression as previously we used bucket names in the request path if not connecting to s3.amazonaws.com.
s3.amazonaws.com
Sorry, something went wrong.
In b2539d5.
Follow-up in #7967.
dkocher
No branches or pull requests
If path value is defined in s3 connection properties this path is used as sumbdomain for server value:
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:
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
The text was updated successfully, but these errors were encountered: