Hey Nirmalya, On Wednesday 20 March 2013 12:34 PM, Nirmalya Lahiri wrote: > Hi all, for last few days I am facing problem while configuring ELB at Amazon > cloud (EC2). The issue is, I am not getting client IP address while I have > configured the ELB listener in Layer 4(TCP) mode in server variable, while I > am getting that in Layer 7(HTTP) mode. I need client IP for my application. > > Still ELB has the issue of SSL/TLS Renegotiation vulnerability. So, I am not > able to use ELB listener in Layer7(HTTP) mode, rather I am using ELB listener > in Layer4(TCP) mode and handle the SSL/TLS Renegotiation vulnerability > through Apache web server. >
Umm, I'm sorry, but I don't know much about the second part -- could you describe what you exactly you mean by SSL/TLS Renegotiation vulnerability. As far as getting the client IP is concerned the 'accepted standard' way of doing this behind an ELB (when using http) is by looking at the X-Forwarded-For header. There are a few quirks you should be aware of but there is enough info available online to help you out. https://www.google.com/search?q=amazon+ELB+X-Forwaded-For cheers, - steve PS: @SK : I think this is a valid question and not OT. What if he had just phrased it differently as "I have a debian EC2 instance running behind an ELB server, which responds to http requests. I need my apache server running on this debian instance to get the client IP ..." ? It is a tech question to do with a linux stack -- it's valid IMHO _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
