We have a aws load balancer. The load balancer uses the TCP connections 443 to encrypt the data.
Since the load balancer encrypts the IP of the client, in our apache log file we can see only the IP of the load balancer rather then the client. Even though we have used %{X-Forwarded-For}i in our log format.
Is there any way to handle this issue?
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.
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
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 generally understand the problems that a load balancer poses for Kerberos. In fact, Microsoft's KB article outright states that it's not possible. However, this article - also on an MS site - suggests that there are possible workarounds.
Has anyone configured a system to use Kerberos and a load balancer? Did you need to use a Forefront server?
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.
Hi,
I have a setup where Apache connects to a F5 load balancer which in turn balances between two jboss app servers.
Apache using mod_proxy -> F5 (hardware load balancer) -> 2 jboss application server
It uses jsessionid. I sometimes get 500 errors for the post methods. I think the request goes to the incorrect jboss server because of the F5 load balancer.
Email this page
