** Also affects: freezer
** Changed in: freezer
Assignee: (unassigned) => Jeremy Liu (liujiong)
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Services should use http_proxy_to_wsgi middleware
Status in Aodh:
Status in Barbican:
Status in Ceilometer:
Status in Cinder:
Status in cloudkitty:
Status in congress:
Status in Freezer:
Status in Glance:
Status in Gnocchi:
Status in heat:
Status in OpenStack Identity (keystone):
Status in Magnum:
Status in neutron:
Status in Panko:
Status in OpenStack Search (Searchlight):
Status in senlin:
Status in OpenStack DBaaS (Trove):
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:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : email@example.com
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp