Girish, That means you are suggesting me to replace ELB with an amazon EC2 instance running relayd as a load-balancer. Am I a correct?
It is not perfect solution. Because Amazon ELB has redundancy support, that means if an ELB somehow goes down another ELB will come alive to support the load-balancing service. If I run a single EC2 instance then how can I overcome from this situation? So, I need a solution without replacing ELB. --Nirmalya ----- Original Message ----- From: Girish Venkatachalam <[email protected]> To: ILUG-C <[email protected]> Cc: Sent: Wednesday, March 20, 2013 1:37 PM Subject: Re: [Ilugc] A serious issue of Amazon Elastic Load Balancer On Wed, Mar 20, 2013 at 1:05 PM, Nirmalya Lahiri <[email protected]> wrote: > > You have to solve the problem by using cookies and custom HTTP headers > to include > the original client IP address before rewriting. > > > The custom HTTP header can added from client side only (as of my knowledge). > But how can I get public IP address if the client is running behind proxy? > > > Can you please explain me the term rewriting? For that what I have to do? I > have to write any code? > You can use openbsd relayd(8) for that. No code. Just configuration. -Girish _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
