We are using aws load-balancer. There is one machine which is behind the load balancer. So for this reason we have configured apache2.conf such that %h are replaced by %{X-Forwarded-For}i in our file.
But something wired is happening. We can't see any ip of the client in the logs section.
But when we change back from %{X-Forwarded-For}i to %h all client ip's are visible in the log section.
I am trying to balance load between two Apache http webservers. I created a load balancer using mod_proxy_balance from apache. When I run my client (which generates around 100s of threads every second and tries to browse through the website), after a few seconds i start getting 502 and 503 error response codes for few threads. There are few other threads that functions properly.
I have heard people say "oh that server is off the load balancer so you can run that expensive script on it".
What implications does a server off the load balancer have? Fundamental to answering this, I understand load balancing, but I don't know what the dynamics of a system with 5 servers (4 on the load balancer) has.
Thanks
Currently I'm using a Cisco CSS hardware load balancer. From the web server's point of view, the end-user's IP address is stamped on all traffic as if the load balancer weren't even present.
I'm now looking at software replacements such as HAProxy, Pound, or AWS ELB. They all have one thing in common: the web server receives the load balancer's IP instead of the end-user's.
If I set up a load balancer on aws that terminates ssl at the load balancer, then the requests being sent to the application server is in plain text. That has definite security implications. How do folks mitigate this implication in practice?
If alternatively, I set up https traffic between load balancer and the application servers also, what are the performance implications?
We're building a load balanced setup with two load balancers (that also terminate SSL) and several upstream servers. Both the load balancers and the upstream servers run nginx. The network on which requests are forwarded to the upstream servers cannot be trusted, hence we have to re-encrypt it after SSL termination on the load balancer.
I have a snapt balancer with one front end listening on port 9055, attached to a backend with only one server at the moment (for testing) also listening on port 9055.
When I go to a browser and type: http://load-balancer-name:9055 the browser shows the page of http://back-end-server:9055 which shows the page I was expecting.
Once that the load balancer contacts the back end server, will the resp
I'm planning to add a hardware load balancer, but I'm not sure if adding one will cause me to lose the ability to restrict traffic by IP ( on folder level by using allow and deny in apache configuration)?
Do you use hardware load balancers to shift traffic with client IP or load balancer IP ?
I am going to host few servers (MS-Windows) listening on certain port to which my clients would connect. I will have to have a load balancer to distribute connections amongst these servers. I have gathered knowledge about load balancer's and have learned few things. But I am not sure if my understanding is correct. Hence, sharing it here so that someone experienced can please verify the same?
Email this page
