On Mon, May 7, 2012 at 10:42 PM, Willy Tarreau wrote:
> Hi Baptiste,
>
> On Thu, May 03, 2012 at 09:50:39PM +0200, Baptiste wrote:
>> When using HAProxy with the option http-server-close or forceclose, haproxy
>> will close the TCP conection on either the server or both the client and
>> the serve
Hi Baptiste,
On Thu, May 03, 2012 at 09:50:39PM +0200, Baptiste wrote:
> When using HAProxy with the option http-server-close or forceclose, haproxy
> will close the TCP conection on either the server or both the client and
> the server, after each request. Which is not compatible with websocket.
On Sat, May 5, 2012 at 10:20 AM, Finn Arne Gangstad wrote:
> You may be hit by the fact that hdr_dom(host) is sort of broken before
> 1.4.18. Some clients include the port number in the Host header, and
> hdr_dom() would not match those. If this is your problem, either upgrade
> haproxy to 1.4.1
You may be hit by the fact that hdr_dom(host) is sort of broken before
1.4.18. Some clients include the port number in the Host header, and
hdr_dom() would not match those. If this is your problem, either upgrade
haproxy to 1.4.18+, 1.5-dev7+, or you can use one of the following
workarounds:
Add
Hello guys,
http-server-close is not a problem; HAProxy supports switching the
protocol when it see an Upgrade header, and websocket works like that
since it has been released as RFC6455. This method (Upgrade header) will
also be used for HTTP/1.1 => HTTP/2.0 migration.
From HAProxy source c
On Thu, May 3, 2012 at 6:48 PM, Francois-Guillaume Ribreau <
francoisguillaume-ribr...@fgribreau.com> wrote:
> In fact I started with an new fresh configuration without all those
> options and now it works well (I still have http-server-close &
> forceclose). But I had to remove the "default_backe
In fact I started with an new fresh configuration without all those options
and now it works well (I still have http-server-close & forceclose). But I
had to remove the "default_backend nginx" directive because it was the root
issue. Sometimes HAProxy was going through the acls (below) without
sele
Thanks for your answer
However, I removed the "mode tcp" line from the frontend block and I still
have the same issue.
Do you have any other ideas ?
Thanks
On Mon, Apr 30, 2012 at 11:20 PM, Baptiste wrote:
> On Mon, Apr 30, 2012 at 3:17 PM, Francois-Guillaume Ribreau
> wrote:
> > On the main
On Mon, Apr 30, 2012 at 3:17 PM, Francois-Guillaume Ribreau
wrote:
> On the main page of my website multiple http requests are made on different
> domains (brin.gr, static.brin.gr and gateway.brin.gr).
> Sometimes everything's fine, sometimes the http request to gateway.brin.gr
> returns 502.
>
>
On the main page of my website multiple http requests are made on different
domains (brin.gr, static.brin.gr and gateway.brin.gr).
Sometimes everything's fine, sometimes the http request to
gateway.brin.grreturns 502.
I've started HAProxy in debug mode and found out that the 502 error occur
when t
10 matches
Mail list logo
