From ef9fa1583466346a914240dd44e79c8237dd6acf Mon Sep 17 00:00:00 2001 From: Christian Schwede Date: Fri, 28 Aug 2015 08:06:23 +0000 Subject: [PATCH] Put staticweb middleware after keystoneauth in proxy pipeline The staticweb middleware needs to be put after authentication middlewares to ensure correct functionality as documented in http://docs.openstack.org/developer/swift/middleware.html#staticweb Without this Swift sends a HTML response even if the request was done using a X-Auth-Token. This might result in a faulty handling of the response on the client side; for example, "swift stat containername" would report an empty, private container, while the container might actually be public readable with data stored in it. --- manifests/proxy/staticweb.pp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manifests/proxy/staticweb.pp b/manifests/proxy/staticweb.pp index 3531751..7fc6a5c 100644 --- a/manifests/proxy/staticweb.pp +++ b/manifests/proxy/staticweb.pp @@ -20,7 +20,7 @@ class swift::proxy::staticweb() { concat::fragment { 'swift-proxy-staticweb': target => '/etc/swift/proxy-server.conf', content => template('swift/proxy/staticweb.conf.erb'), - order => '32', + order => '82', } } -- 1.9.1