Re:RE:MG TV factory from China

2014-01-23 Thread TV factory
Dear  Purchasing Manager, How are you ?   MG Electronic manufacture Limited Company  is one of the top Electronic LCD TV and LED TV,3D TV and Smart TV Manufacturers and Exporters which located in Guangdong province of China. Our main products cover LCD TV from 15~65 inc

SIGQUIT, silence

2014-01-23 Thread Jim Freeman
Using haproxy-1.5-dev19 on Debian/Wheezy, and haproxy-1.5-dev21 on CentOS6.2, killing haproxy with SIGQUIT gets me nothing in the system logs. SIGHUP gets proxy/server status info into the logs just fine. I'm using them the same way, but SIGQUIT seems to just do ... nothing? Nut loose on the keyb

Re: updated instructions for tproxy and haproxy

2014-01-23 Thread Baptiste
Hi Zach, You can use this link as well: http://blog.exceliance.fr/2013/09/16/howto-transparent-proxying-and-binding-with-haproxy-and-aloha-load-balancer/ Baptiste On Thu, Jan 23, 2014 at 9:11 PM, Buckholz, Zachary wrote: > I need to forward the client IP for ssh connections to a backend git ser

updated instructions for tproxy and haproxy

2014-01-23 Thread Buckholz, Zachary
I need to forward the client IP for ssh connections to a backend git server. Is the following link still the best source of documentation on how to do this? http://blog.loadbalancer.org/configure-haproxy-with-tproxy-kernel-for-full-transparent-proxy/ Or is there a more upto date method now? Than

determine size of http headers

2014-01-23 Thread Patrick Hemmer
What I'd like to do is add a few items to the log line which contain the size of the headers, and then the value of the Content-Length header. This way if the connection is broken for any reason, we can determine if the client sent all the data they were supposed to. Logging the Content-Length hea

Re: memory usage with 1.5dev21

2014-01-23 Thread Thomas Heil
Hi, On 23.01.2014 16:43, Baptiste wrote: > Hi Thomas, > > Please share your configuration (anonymized). > Ive attached the config. > Baptiste > thanks, thomas > On Thu, Jan 23, 2014 at 1:28 PM, Thomas Heil > wrote: >> > Hi, > > We are running in haproxy 1.5dev21 commit > fa7fc95e16fae8b30f2522f5

Re: memory usage with 1.5dev21

2014-01-23 Thread Baptiste
Hi Thomas, Please share your configuration (anonymized). Baptiste On Thu, Jan 23, 2014 at 1:28 PM, Thomas Heil wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > We are running in haproxy 1.5dev21 commit > fa7fc95e16fae8b30f2522f59bb945c596e48419. I see very high memory > us

Plus Jamais Froid en Hiver

2014-01-23 Thread CGR GOLF
Si ce message ne s'affiche pas correctement consultez-le en ligne Pour être sûr de recevoir nos newsletters, merci d'ajouter notre adresse email bouti...@cgrgolf.fr à vos contacts. www.cgrgolf.fr Rejoignez-nous sur Veuillez me retirer de votre liste de diffusion

memory usage with 1.5dev21

2014-01-23 Thread Thomas Heil
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, We are running in haproxy 1.5dev21 commit fa7fc95e16fae8b30f2522f59bb945c596e48419. I see very high memory usage just after 5 days. - -- uptime5d 14h 48m children 0 memory kilobytes

RE: tune.bufsize issue with send-proxy / accept-proxy SSL setup

2014-01-23 Thread Oskar Liljeblad
Ah, sorry, I was using the one in Debian (experimental) from 2013-12-17. When I upgraded to 2014-01-18 (1.5~dev21+20140118-1) then the problem did not persist! Thanks for the information! Regards, Oskar -Original Message- From: Baptiste [mailto:bed...@gmail.com] Sent: Thursday, Januar

Re: tune.bufsize issue with send-proxy / accept-proxy SSL setup

2014-01-23 Thread Baptiste
Hi Oskar, Are you using the latest git version? If no, please give it a try, there may be a fix which apply to this case. Baptiste On Thu, Jan 23, 2014 at 12:22 PM, Oskar Liljeblad wrote: > Hello > > > > Our HAProxy 1.5~dev21 setup looks like this: > > > > client browser -> haproxy1 -> haprox

tune.bufsize issue with send-proxy / accept-proxy SSL setup

2014-01-23 Thread Oskar Liljeblad
Hello Our HAProxy 1.5~dev21 setup looks like this: client browser -> haproxy1 -> haproxy2 -> web servers - client browser sends as https. - haproxy1 receives with mode tcp frontend, and sends using mode tcp backend with send-proxy. - haproxy2 receives with mode http frontend with ssl accept-pro