Comment 4 for bug 1843577

currently, except for traffic from internal checks, all traffic from customers passes through haproxy, and I in the flight on haproxy overwrites the X-Forwarder-For header so there is no risk of the client heading falsification. It would be good if you could set swift-proxy to parse any header I set to haproxy or at least X-Forwarder-For. This would make life a lot easier, because when I turned the "require_proxy_protocol" variable to true, all my internal checks must talk with the proxy protocol, but not all of them can.