Hello, > Is there a chance to slip in a fix to this issue (I wrote about it few > week ago): > http://librelist.com/browser//mongrel2/2012/4/26/x-forwarded-for-header-behind-elb/#c10ea83e001c8ca39f4f94518d105a49 > and was raised here to: > http://librelist.com/browser//mongrel2/2012/3/2/mongrel2-and-http-headers/#07902972ea65c53e23891f4c9f6d9448 > > I wrote the code to fix it by appending to the x-forwarded-for header > instead of overwriting it, however I did not make any pull request since > I think there should be some agreement regarding how to do it - append > to the x-forwarded-for header or using a REMOTE_IP header.
this is why we want the 1.8 out asap, to have a clear path for the way we handle headers in the future. We may even change the format (one dict for the headers from the client, one for data from M2 and then the payload). Basically, 1.8 is out without changes and then we can discuss and implement the best solution for the long term. loïc
