
HEAD requests to S3 respond with the exact same header as a GET, swift3 responds with an incorrect Content-Type and Content-Length. A quick hack to fix this issue is below, but should probably be replaced with something involving DiskFile and such from Swift's API, because of innecessary overhead involved in reading in the file. Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Swift3
Swift3 Middleware for OpenStack Swift, allowing access to OpenStack swift via the Amazon S3 API.
Install
-
Install Swift3 with
sudo python setup.py install
orsudo python setup.py develop
or via whatever packaging system you may be using. -
Alter your proxy-server.conf pipeline to have swift3:
Was::
[pipeline:main] pipeline = catch_errors cache tempauth proxy-server
Change To::
[pipeline:main] pipeline = catch_errors cache swift3 tempauth proxy-server
-
Add to your proxy-server.conf the section for the Swift3 WSGI filter::
[filter:swift3] use = egg:swift3#swift3
Description
Swift3 Middleware for OpenStack Swift, allowing access to OpenStack swift via the Amazon S3 API.
Languages
Python
99.3%
Shell
0.7%