Suggestion: Customisable style sheet

2010-03-18 Thread Balcoes
Hi. I am sorry if this subject has been discussed before... I have dedicated one monitor to HAproxy's status page. However as it is now the name given in the config file's listen line is dark red. And red is usually associated with problem situations. So at a quick glance I have many times

Re: Throughput degradation after upgrading haproxy from 1.3.22 to 1.4.1

2010-03-18 Thread Erik Gulliksson
Hi, Did you observe anything special about the CPU usage ? Was it lower than with 1.3 ? If so, it would indicate some additional delay somewhere. If it was higher, it could indicate that the Transfer-encoding parser takes too many cycles but my preliminary tests proved it to be quite

Re: Throughput degradation after upgrading haproxy from 1.3.22 to 1.4.1

2010-03-18 Thread Malte Geierhos
Hello, Unfortunately I the show errors returned empty, so I guess it was something else. The good news is that I gave haproxy 1.4.2 a try today and the 502/PR error with PUT/TE:chunked requests have now vanished. So thanks for solving this. I'm not sure which one of the bugs I was hitting

Re[2]: [ANNOUNCE] haproxy-1.4.2

2010-03-18 Thread Ross West
HJ By compiling Haproxy 1.4.2 on Opensolaris b134 I noticed a warning in HJ dumpstats.c. I don't know for sure if this is a problem, but I thought I HJ let you know. Got the same on Freebsd - but a touch more descriptive message. -= start gcc -Iinclude -Iebtree -Wall -O2 -g -DTPROXY

Re: Throughput degradation after upgrading haproxy from 1.3.22 to 1.4.1

2010-03-18 Thread Willy Tarreau
Hi Erik, On Thu, Mar 18, 2010 at 02:29:46PM +0100, Erik Gulliksson wrote: Unfortunately I the show errors returned empty, so I guess it was something else. The good news is that I gave haproxy 1.4.2 a try today and the 502/PR error with PUT/TE:chunked requests have now vanished. So thanks for

Re: Throughput degradation after upgrading haproxy from 1.3.22 to 1.4.1

2010-03-18 Thread Erik Gulliksson
Hi Malte, So now when I got a working haproxy 1.4, I continued to try out the option http-server-close but I hit a problem with our stunnel (patched with stunnel-4.22-xforwarded-for.diff) instances. It does not support keep-alive, so only the first HTTP request in a keepalive-session gets

Re: Throughput degradation after upgrading haproxy from 1.3.22 to 1.4.1

2010-03-18 Thread XANi
So now when I got a working haproxy 1.4, I continued to try out the option http-server-close but I hit a problem with our stunnel (patched with stunnel-4.22-xforwarded-for.diff) instances. It does not support keep-alive, so only the first HTTP request in a keepalive-session gets the

Re: Throughput degradation after upgrading haproxy from 1.3.22 to 1.4.1

2010-03-18 Thread Erik Gulliksson
Hi Willy On Thu, Mar 18, 2010 at 3:08 PM, Willy Tarreau w...@1wt.eu wrote: OK so very likely it's the same problem I fixed yesterday using Bernhard's captures. Great! Thanks to Bernhard as well then, for providing you with the captures. yes indeed it's expected. Stunnel is not designed to

Fw: Notification of Protection for Google Search Right About formilux

2010-03-18 Thread Martin
Dear , I got your email address from my colleague, saying that you are the person in charge. We are a professional internet service provider organization in Asia, having the business around the world. Recently we have received an application from one of our customer Loquen LTD, who have