From a4625e7e7f9fe6da7a671339e8a5a81bc0e5299a Mon Sep 17 00:00:00 2001 From: Juan Antonio Osorio Robles Date: Wed, 20 Jul 2016 15:06:36 +0300 Subject: [PATCH] Add reno notes about http_proxy_to_wsgi middleware This note is meant for Id33a0f7eeb8ced77d09f9edd6b1d65697d8bcfe7 Change-Id: Ifee7256a67a2a9722879e85b109258f05fb1f349 --- ...o_wsgi-instead-of-ssl-middleware-df533a2c2d9c3a61.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 releasenotes/notes/Use-http_proxy_to_wsgi-instead-of-ssl-middleware-df533a2c2d9c3a61.yaml diff --git a/releasenotes/notes/Use-http_proxy_to_wsgi-instead-of-ssl-middleware-df533a2c2d9c3a61.yaml b/releasenotes/notes/Use-http_proxy_to_wsgi-instead-of-ssl-middleware-df533a2c2d9c3a61.yaml new file mode 100644 index 0000000000..1d55c0ba0d --- /dev/null +++ b/releasenotes/notes/Use-http_proxy_to_wsgi-instead-of-ssl-middleware-df533a2c2d9c3a61.yaml @@ -0,0 +1,8 @@ +--- +security: + - http_proxy_to_wsgi is taken into use instead of the deprecated ssl + middleware. This makes it easier for deployers to have Manila running + behind a proxy that terminates TLS connections. This middleware addition + adds the enable_proxy_headers_parsing option to the oslo_middleware section + which needs to be set in the configuration file in order to enable + middleware to do its work.