From 856d869a040695aea876c6ff93dbe4889a03ad1a Mon Sep 17 00:00:00 2001 From: Christian Schwede Date: Wed, 28 Jan 2015 15:19:46 +0100 Subject: [PATCH] Fix staticweb middleware position in the pipeline Listing objects in a container fails using the CLI if the staticweb middleware is located before the Keystone middlewares. The staticweb is by default only enabled for anonymous requests, thus currently all requests will be handled by the staticweb middleware instead of the proxy server. Placing the middleware after the authentication middlewares prevents this. Change-Id: I123959cf2e45143e91a997cda16b8aac50aaea08 --- manifests/object/controller.pp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manifests/object/controller.pp b/manifests/object/controller.pp index 16f5c6b0..98f9e1ef 100644 --- a/manifests/object/controller.pp +++ b/manifests/object/controller.pp @@ -102,7 +102,7 @@ class cloud::object::controller( pipeline => [ 'catch_errors', 'healthcheck', 'cache', 'bulk', 'ratelimit', 'swift3', 's3token', 'container_quotas', 'account_quotas', 'tempurl', - 'formpost', 'staticweb', 'ceilometer', 'authtoken', 'keystone', + 'formpost', 'ceilometer', 'authtoken', 'keystone', 'staticweb', 'proxy-logging', 'proxy-server'], account_autocreate => true, log_level => 'DEBUG',