yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #57598
[Bug 1590608] Re: Services should use http_proxy_to_wsgi middleware
** Also affects: neutron
Importance: Undecided
Status: New
** Also affects: aodh
Importance: Undecided
Status: New
** Also affects: ceilometer
Importance: Undecided
Status: New
** Also affects: gnocchi
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1590608
Title:
Services should use http_proxy_to_wsgi middleware
Status in Aodh:
New
Status in Barbican:
New
Status in Ceilometer:
New
Status in Cinder:
Fix Released
Status in Glance:
Fix Released
Status in Gnocchi:
New
Status in OpenStack Identity (keystone):
Fix Released
Status in neutron:
In Progress
Status in OpenStack DBaaS (Trove):
In Progress
Bug description:
It's a common problem when putting a service behind a load balancer to
need to forward the Protocol and hosts of the original request so that
the receiving service can construct URLs to the loadbalancer and not
the private worker node.
Most services have implemented some form of secure_proxy_ssl_header =
HTTP_X_FORWARDED_PROTO handling however exactly how this is done is
dependent on the service.
oslo.middleware provides the http_proxy_to_wsgi middleware that
handles these headers and the newer RFC7239 forwarding header and
completely hides the problem from the service.
This middleware should be adopted by all services in preference to
their own HTTP_X_FORWARDED_PROTO handling.
To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1590608/+subscriptions
References