Hi Hank,
On Sun, Jun 27, 2010 at 02:12:35PM -0700, Hank A. Paulson wrote:
> I got this error hit via the haproxy socket, I noticed that there are
> a few hits when searching for it, all related to corrupt headers with
> lighttpd and people seem to be assuming it is lighttpd's fault but in
> the ca
On Mon, Jun 28, 2010 at 06:39:37AM +0300, grigorov.hrist...@neftochim.bg wrote:
>
> Thank you Willy, that will do it if you say however I had the impression that
> HAproxy by default won't use backend that is currently down. For that a new
> session (redirect) always gets backend that is online
Thank you Willy, that will do it if you say however I had the impression that
HAproxy by default won't use backend that is currently down. For that a new
session (redirect) always gets backend that is online unless all are down in
which case error page is something very much acceptable.
If I
I got this error hit via the haproxy socket, I noticed that there are a few
hits when searching for it, all related to corrupt headers with lighttpd and
people seem to be assuming it is lighttpd's fault but in the case I received,
it is clear that there are some junk characters at the beginning
On Sun, Jun 27, 2010 at 08:46:59PM +0300, grigorov.hrist...@neftochim.bg wrote:
>
> May be I am using this option for wrong purpose but it works nicely when at
> least one backend is available. User is auto-redirected withount any boring
> error pages. Problem happens only when all backends are
May be I am using this option for wrong purpose but it works nicely when at
least one backend is available. User is auto-redirected withount any boring
error pages. Problem happens only when all backends are down.
From: Willy Tarreau [mailto:w...@1wt.eu]
Se
6 matches
Mail list logo
