On Monday 19 of September 2011 06:18:45 Willy Tarreau wrote:
frontend xxx
bind 1.2.3.4:80
bind /var/run/haproxy/sock-xxx accept-proxy
But this requires that the ssl termination supports unix sockets and I
believe that stud currently does not.
Just a quick question, Willy;
On Mon, Sep 19, 2011 at 09:54:16AM +0200, Brane F. Gra??nar wrote:
On Monday 19 of September 2011 06:18:45 Willy Tarreau wrote:
frontend xxx
bind 1.2.3.4:80
bind /var/run/haproxy/sock-xxx accept-proxy
But this requires that the ssl termination supports unix sockets and
Hey Willy,
So we are now hit by the side effect of this fix i.e. disabling httpclose.
Two problems:
1. Entries in the log are missing, I guess you already warned me about it.
Do you think if we disable keep alive in our Apache fronting haproxy, this
will problem will go away?
2. Related to
Hi there,
Finally, we've finished our bench on SSL tools available for HAProxy:
stud and stunnel.
Please read the benchmark here:
http://blog.exceliance.fr/2011/09/16/benchmarking_ssl_performance/
cheers
Hi,
Is there a caching system at HAProxy?
In fact, we find that when we put online new files (CSS, for example) that they
are not addressed directly, it usually takes about ten minutes.
Thank you in advance for your help.
Christophe
Hi,
I thought the problem was in my browser but when I empty the cache, I've
the same problem.
To be sure, I tried with an other browser and the problem is the same.
When I call my page locally from the server, the result is OK.
Christophe
Le 19/09/11 13:45, « Baptiste » bed...@gmail.com a
In any case HAProxy can be pointed about this problem.
Do you have a proxy on your LAN?
or Apache mod_cache enabled?
cheers
On Mon, Sep 19, 2011 at 2:30 PM, Christophe Rahier
christo...@qualifio.com wrote:
Hi,
I thought the problem was in my browser but when I empty the cache, I've
the
On 09/08/2011 02:20 AM, Willy Tarreau wrote:
On Tue, Sep 06, 2011 at 07:01:44PM -0400, Chris Burroughs wrote:
On 09/01/2011 09:04 PM, Chris Burroughs wrote:
I've looked at the source code and I think that's what's going on, but
it has been a while since I've read C networking code.
You can get weird results like this sometimes if you don't use http-close or
any other http closing option on http backends. You should paste your config.
Maybe there should be a warning, if there is not already, for that situation -
maybe just when running -c.
On 9/19/11 5:46 AM, Christophe
We are running haproxy at amazon and running some load tests and seem to be
hitting some bottleneck between haproxy and webservers or haproxy itself.
How can you tell when haproxy is maxed out? Will cpu hit 100% or is it some
other characteristic? our cpu is 4% and I only have 10 webservers and
Hi Sachin,
On Mon, Sep 19, 2011 at 01:47:28PM +0530, Sachin Shetty wrote:
Hey Willy,
So we are now hit by the side effect of this fix i.e. disabling httpclose.
Two problems:
1. Entries in the log are missing, I guess you already warned me about it.
Do you think if we disable keep
11 matches
Mail list logo