Tag Info

Hot answers tagged

6

When I resolve your domain name, I get back three different AAAA records: www6.plista.com. 1800 IN AAAA 2a01:4f8:160:5102::2 www6.plista.com. 1800 IN AAAA 2a01:4f8:151:5021::2 www6.plista.com. 1800 IN AAAA 2a01:4f8:191:8075::2 I can only reach one of those IP addresses (2a01:4f8:160:5102::2). When I ...


2

I had the same problem as @tom-angelo-clemente, but solved it by using the broadcast address on the bind parameter of a frontend: frontend wfe bind 0.0.0.0:80 This will bind the proxy to any IP address the machine is using (not sure about addresses on different NIC devices), so be careful when using this way if you have a private management interface ...


2

There is no API or anyway to do what you want. You need to add the backends into the config and do a graceful reload. What that does is it spins off another haproxy process to handle the traffic and the other process waits till it finishes and quits. You should be able to reload haproxy with no connection refused or bad requests.


2

Nice picture :) timeout connect is on server side, it is the maximum time to run the TCP handshake http-request starts from the ACK on the client side until whole HTTP headers have been received Tq starts from the client Handshake TCP. Tr is until we receive the response Headers Baptiste


2

I don't know of an existing tool offhand. But you can take the work done with this logstash grok regex, convert to a regex in the language of your choice and spit out the object as csv.


2

As it turns out I was very close to a working config. Changing the redirect line to read redirect prefix / code 301 if old_url made it work as expected. I wrote a blog post which outlines the problem in a little more detail: http://fromanegg.com/post/105250564587/how-to-rewrite-and-redirect-with-haproxy


1

The easiest solution is to use balance source, but if many clients come from the same IP, it may not be very fair on your backend servers. See http://blog.haproxy.com/2013/04/22/client-ip-persistence-or-source-ip-hash-load-balancing/ for more discussion on methods to accomplish this.


1

Two haproxy instances can share load by using 2 virtual IPs with each instance the master for one of those. Round robin DNS roughly balances between the 2 virtual IPs (and consequently between the two haproxy instances). This method also works with SSL. One reason to think twice about this active-active setup though is if one instance can't cope with the ...


1

Running haproxy in foreground (haproxy -d -V -f haproxy.cfg) with your sample displayed the following warning: acl 'some_condition' will never match because it only involves keywords that are incompatible with 'frontend http-response header rule' Fiddling with my config, I found that this warning is displayed when using this ACL: acl some_condition ...


1

All other answers are pre-2010, hence adding an updated comparison. Nginx A full web server, other features can also be used. Eg: HTTP Compression SSL Support Very light weight as Nginx was designed to be light from the start. Near Varnish caching performance Close to HAProxy load balancing performance Varnish best for complex caching scenarios and ...



Only top voted, non community-wiki answers of a minimum length are eligible