Sorry for the long delay, I have not had time to get back to this until now.
Yes, it works with the extra slash and my PCI compliance scanning is
happy again.
rspirep ^Set-Cookie:\ (cookieName.*)Set-Cookie:\ \1;\ HttpOnly
Thanks for your help, it is much appreciated.
Regards,
Duncan
O
Are you using keepalive on haproxy? Perhaps you are confronting nginx with
keepalive enabled and haproxy with client-side keepalive disabled?
Can you share the haproxy config?
Thomas is right, you should probably unload conntrack for best performance.
Also make sure you don't have any network
Hi,
On 06.03.2013 16:58, Olivier Desport wrote:
> I've found the solution. I have enabled the line EXTRAOPTS="-de -m 16"
> in /etc/default/haproxy. It works when this line is commented.
>
That means, you gave haproxy only 16MB of memory for his hard work.
Maybe this was not enough.
> Thanks for
Hi,
On 06.03.2013 16:27, Alexandru Florescu wrote:
>
> Hi,
> I have a 3 server architecture, a HAproxy that sends balanced traffic
> to 2 Nginx servers.
>
> I noticed that if I run "ab -n 1000 -c 100" directly on the Nginx
> server I get response times between 40 and 80ms
> If I run the same test
I've found the solution. I have enabled the line EXTRAOPTS="-de -m 16"
in /etc/default/haproxy. It works when this line is commented.
Thanks for your help.
Le 23/01/2013 17:13, shouldbe q931 a écrit :
Hi Olivier,
Just to recap, you have a webserver in subnet A, you have a HAProxy
instance
Hi,
I have a 3 server architecture, a HAproxy that sends balanced traffic to
2 Nginx servers.
I noticed that if I run "ab -n 1000 -c 100" directly on the Nginx server
I get response times between 40 and 80ms
If I run the same test via HAproxy I receive results between 120 and
4000ms. And thi
Hi,
Maybe DNS resolution has expired and HAProxy gets a NXdomain when it
tries to resolve it.
Baptiste
On Wed, Mar 6, 2013 at 2:06 PM, Matthieu Boret wrote:
> Hi,
>
> I have a strange and random problem with Haproxy. Sometimes, I have an error
> when I'm trying to reload the configuration file.
Amazon have probably removed the DNS after it's been offline for over a
certain period of time.
Chris
On 06/03/2013 13:06, Matthieu Boret wrote:
Hi,
I have a strange and random problem with Haproxy. Sometimes, I have an
error when I'm trying to reload the configuration file.
Reloading hapr
Hi,
I'm currently upgrading from postfix 2.9 to 2.10 with haproxy 1.5-dev17
So far, everythink works fine with:
:/etc/haproxy/haproxy.cfg:
frontend ft_smtps
bind :465
mode tcp
default_backend bk_smtps
frontend ft_submission
bind :587
mode tcp
default_backend bk_submissi
9 matches
Mail list logo