Comment 2 for bug 1489749

Hmm, this is tricky and might affect a few more users. Not yet adding openstack/puppet-swift; however I attached a patch ready for this as well.

openstack/puppet-swift puts staticweb in front of keystone in the proxy pipeline; not sure how many operators use this module, but this might result in a much wider distribution of the problem #2.

https://github.com/openstack/puppet-swift/blob/master/manifests/proxy/staticweb.pp#L23
https://github.com/openstack/puppet-swift/blob/master/manifests/proxy/keystone.pp#L35

In fact other middlewares might be not in the correct pipeline order as well, but that seems to be a different problem:

vagrant@saio:~/puppet-swift$ grep order manifests/proxy/* | sort -t ':' -k 2 | cut -f 3- -d "/"
tempauth.pp: order => '01',
swauth.pp: order => '20',
bulk.pp: order => '21',
authtoken.pp: order => '22',
cache.pp: order => '23',
catch_errors.pp: order => '24',
healthcheck.pp: order => '25',
ratelimit.pp: order => '26',
proxy_logging.pp: order => '27',
swift3.pp: order => '27',
s3token.pp: order => '28',
tempurl.pp: order => '29',
formpost.pp: order => '31',
staticweb.pp: order => '32',
ceilometer.pp: order => '33',
gatekeeper.pp: order => '34',
crossdomain.pp: order => '35',
slo.pp: order => '35',
keystone.pp: order => '79',
account_quotas.pp: order => '80',
container_quotas.pp: order => '81',