Re: [PATCH] MAJOR: ssl: add 'tcp-fallback' bind option for SSL listeners

Le 28/02/2016 23:32, PiBa-NL a écrit : > Hi Christopher, Willy, > > I've created a patch that can be applied on top of your tcp-fallback > patch to allow for 'conditional' offloading. > It shows 'ability' to have both offloading and pass-trough for ssl > depending on a sni name or other acl

Re: Haproxy 1. 5.14 + Tomcat 8 giving random 502 errors

Hi. Am 02-03-2016 07:48, schrieb Zoltan Lorincz: Jeff, thanks again for the detailed answer. I've already tested a configuration without various ACL's. Please can you try to run the connector with debug on.

"Odd" behaviour on resolvers

Hi there, First of all : I am very fond of HAProxy :-) I was trying to do some service discovery with bind9 and HAProxy when I found an odd behaviour on the /resolvers/ part. Here are some config samples : My frontend and backend and resolvers config: /resolvers discovery// //

Re: "Odd" behaviour on resolvers

During configcheck the resolver portion of haproxy is not yet active. Thus during the check it uses the system resolver. Once actually running it will use the resolver from haproxy. On Mar 4, 2016 16:26, "Arnaud B." wrote: Hi there, First of

Re: Client timeout expiring while waiting for server response

Hi Lukas, I did try increasing "timeout http-keep-alive", without any effect. I'm attaching a tcpdump from the client side. For this capture I had the client timeout at 10 seconds rather than 5, but the effect is the same. You can also see that, even though the client timeout triggered, the

Client timeout expiring while waiting for server response

Hi, I'm having an issue with the client timeout expiring unexpectedly. I am using haproxy v1.5.14 with the http-keep-alive option. In my use case, I have a client maintaining a long-lived connection through haproxy to a backend server. The backend server sends back a response 30 seconds after

RE: Client timeout expiring while waiting for server response

Hi Francois, > Hi, > > I'm having an issue with the client timeout expiring unexpectedly. > > I am using haproxy v1.5.14 with the http-keep-alive option. > > In my use case, I have a client maintaining a long-lived connection > through haproxy to a backend server. The backend server sends back a

3 devis pour changer vos fenêtres et faire jusqu'a 50 pourcent d'économies

Afficher la version web. (http://trk.mix.jajaris.fr/view/y2g-89jgr.php) | Annuler votre abonnement. (http://trk.mix.jajaris.fr/usb/y2g-89jgr.php) | Signaler comme courrier indésirable. (mailto:ab...@dgcnit.fr)

Re: "Odd" behaviour on resolvers

So there is no way to use a resolver that is not used by the system on haproxy's start ? Le 04/03/2016 17:32, Robin Geuze a écrit : > > During configcheck the resolver portion of haproxy is not yet active. > Thus during the check it uses the system resolver. Once actually > running it will use