b0d0b1d0ba
The HTTP_X_FORWARDED_PROTO handling fails to handle the case of redirecting the /v1 request to /v1/ because it is handled purely by routes and does not enter the glance wsgi code. This means a https request is redirect to http and fails. oslo.middleware has middleware for handling the X-Forwarded-Proto header in a standard way so that services don't have to and so we should use that instead of our own mechanism. Leaving the existing header handling around until removal should not be a problem as the worst that will happen is it overwrites an existing 'https' header value set by the middleware. Closes-Bug: #1558683 Closes-Bug: #1590608 Change-Id: I481d88020b6e8420ce4b9072dd30ec82fe3fb4f7
15 lines
397 B
Plaintext
15 lines
397 B
Plaintext
[DEFAULT]
|
|
output_file = etc/glance-api.conf.sample
|
|
namespace = glance.api
|
|
namespace = glance.store
|
|
namespace = oslo.concurrency
|
|
namespace = oslo.messaging
|
|
namespace = oslo.db
|
|
namespace = oslo.db.concurrency
|
|
namespace = oslo.policy
|
|
namespace = keystonemiddleware.auth_token
|
|
namespace = oslo.log
|
|
namespace = oslo.middleware.cors
|
|
namespace = oslo.middleware.http_proxy_to_wsgi
|
|
namespace = osprofiler
|