yahoo-eng-team team mailing list archive

[OpenStack Infra <1590608@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/386990
Committed: https://git.openstack.org/cgit/openstack/freezer-api/commit/?id=fbd1f04abf997ca6a079a9d97f954aabe194bd57
Submitter: Jenkins
Branch:    master

commit fbd1f04abf997ca6a079a9d97f954aabe194bd57
Author: Jeremy Liu <liujiong@xxxxxxxxxxxxx>
Date:   Sun Oct 16 11:13:03 2016 +0800

    Use http_proxy_to_wsgi middleware
    
    This sets up the HTTPProxyToWSGI middleware in front of Freezer.
    The purpose of this middleware is to set up the request URL
    correctly in case there is a proxy (For instance, a loadbalancer
    such as HAProxy) in front of Freezer.
    
    The HTTPProxyToWSGI is off by default and needs to be enabled
    via a configuration value.
    
    Depends-On: Iffd38a325204a3ec7380a7a56061866477d3d06e
    Change-Id: I44d60863eefeb52891474653aa9fcf1ba57d50a1
    Closes-bug: #1590608


** Changed in: freezer
       Status: In Progress => Fix Released

-- 
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:
  Fix Released
Status in Barbican:
  In Progress
Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in cloudkitty:
  In Progress
Status in congress:
  New
Status in Freezer:
  Fix Released
Status in Glance:
  Fix Released
Status in Gnocchi:
  Fix Committed
Status in heat:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in Magnum:
  New
Status in neutron:
  Fix Released
Status in Panko:
  Fix Released
Status in Sahara:
  In Progress
Status in OpenStack Search (Searchlight):
  In Progress
Status in senlin:
  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