HAProxy SSL Terminatio: X-Forward-Proto

Bug #1646593 reported by Mathias Ewald
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Medium
Mathias Ewald

Bug Description

Currently, HAProxy sets X-Forward-Proto to "https" if HAProxy manages SSL termination. The header is deleted independently of this.

This breaks situations where we use HAProxy to load balance OpenStack traffic but place a reverse proxy in between the internet and HAProxy which performs SSL termination.

HAProxy will then delete the header which was set by the reverse proxy.

Mathias Ewald (mewald)
Changed in kolla:
assignee: nobody → Mathias Ewald (mewald)
Changed in kolla:
status: New → Triaged
importance: Undecided → Medium
Changed in kolla:
milestone: none → ocata-3
Changed in kolla:
milestone: ocata-3 → ocata-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 4.0.0.0rc1

This issue was fixed in the openstack/kolla-ansible 4.0.0.0rc1 release candidate.

Changed in kolla:
milestone: ocata-rc1 → pike-1
Changed in kolla:
milestone: pike-2 → pike-3
Changed in kolla:
milestone: pike-3 → pike-rc1
Changed in kolla:
milestone: pike-rc1 → queens-1
Changed in kolla:
milestone: queens-2 → queens-3
Changed in kolla:
milestone: queens-3 → queens-rc1
Mathias Ewald (mewald)
Changed in kolla:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.