RE: Error responses in statistics

2009-10-12 Thread Stefan Johansson
Willy, I noticed that we had the dontlognull option already set, but we obviously still get these messages. Regards, Stefan > Date: Mon, 5 Oct 2009 09:41:57 +0200 > From: w...@1wt.eu > To: phu...@hotmail.com > CC: haproxy@formilux.org > Subject: Re: Error responses in statistics > > O

Small patch for the "appsession" feature

2009-10-12 Thread Cyril Bonté
Hello, as discussed previously with Willy Tarreau, I'd like to propose a patch for the appsession code. This patch has 2 goals : 1. I wanted to test the appsession feature with a small PHP code, using PHPSESSID. The problem is that when PHP gets an unknown session id, it creates a new one with

Re: Small patch for the "appsession" feature

2009-10-12 Thread Aleksandar Lazic
Hi Cyril, good catch. On Mon 12.10.2009 23:03, Cyril Bonté wrote: Hello, as discussed previously with Willy Tarreau, I'd like to propose a patch for the appsession code. This patch has 2 goals : [snipp] diff -Naur haproxy-1.4-dev4/src/proto_http.c haproxy-1.4-dev4-appsession/src/proto_http

[PATCH] [MINOR] CSS & HTML fun

2009-10-12 Thread Krzysztof Piotr Oledzki
>From 6fc49b084ad0f4513c36418dfac1cf1046af66da Mon Sep 17 00:00:00 2001 From: Krzysztof Piotr Oledzki Date: Mon, 12 Oct 2009 23:09:08 +0200 Subject: [MINOR] CSS & HTML fun This patch makes stats page about 30% smaller and "CSS 2.1" + "HTML 4.01 Transitional" compliant. There should be no visible

Re: multiple applications using HAproxy LB

2009-10-12 Thread Ryan Schlesinger
It sounds like what you really want is to put apache (or some other web server) in front of haproxy to do name based virtual hosting. Requests for your two domains would work like this: client -> apache:80 (domain1 virtual host) -> haproxy:8080 client -> apache:80 (domain2 virtual host) -> hap

Re: multiple applications using HAproxy LB

2009-10-12 Thread Aleksandar Lazic
On Mon 12.10.2009 14:42, Ryan Schlesinger wrote: It sounds like what you really want is to put apache (or some other web server) in front of haproxy to do name based virtual hosting. Requests for your two domains would work like this: client -> apache:80 (domain1 virtual host) -> haproxy:8080 c

Re: Problems with long connect times

2009-10-12 Thread Hank A. Paulson
A couple of guesses you might look at - I have found the stats page to show deceptively low numbers at times. You might want to check the http log stats that show the global/frontend/backend queue numbers around the time those requests. My guess is that the cases where you are seeing 3 second ti