| cmarbach | |
| Jun 4 2025, 11:14 AM |
| F15035865: image.png | |
| Jun 4 2025, 2:04 PM |
Summary
Add a feature in the load-balancing haproxy that enables the X-Forwarded-For http header on the backend service.
*Use case**
X-Forwarded-For http header is useful to keep track of real IP of client even when it traverses a reverse proxy.
Additional information
Well, it could be an option in the load-balancing haproxy service definition, something like "option forwardedfor" that would enable the http header and feed it with real client IP.
It already should work if the backend mode http https://github.com/vyos/vyos-1x/blob/a711ceb80158a1dcdeecd1570ca705684d636327/data/templates/load-balancing/haproxy.cfg.j2#L199-L203
Can you re-check?
You're right, headers for port and protocol are being added but not the host.
I'm speaking about the X-Forwarded-For http header, see Mozilla reference for example.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Forwarded-For
Sorry, my bad, capturing traffic send from the haproxy to the backend actually contains the X-Forwarded-For header. Simply close my request and thanks for the quick answer / interaction.
