> OK just to be sure, you should *really* make your changes on 1.5-dev, not > 1.4. 1.4 is in deep maintenance mode and I don't intend to merge such > changes there, as every time I did I caused some regressions.
I'm in process of porting my patch to 1.5. I don't particularly want to run 1.5 in production though, and it occurs to me that my patch is quite involved for what I'm trying to accomplish. My goal is essentially to have the remote ip of the upstream client available to my application (sitting behind haproxy). For http backends, I can use forwardfor and it works great. However, this specific service is raw tcp. I know I can use tproxy, but would prefer to avoid upgrading my kernel and setting up additional iptables rules. The idea with this patch was that the application could connect to haproxy to get events and use that data to figure out the upstream client's ip. This adds a lot of complexity though, so I'm trying to come up with alternatives. The only other obvious solution is to have haproxy prepend something to the tcp stream. In my case this will work fine, since I can modify my application to extract this from the stream before consuming the client data. Is this generic enough to add as a feature to haproxy? How would it look ideally.. something like `option prepend "%inbound_peer\000"`? Aman
