Re: [PATCH 1/1] MINOR: cli: Dump all resolvers stats if no resolver

Thanks! On Tue, Oct 6, 2015 at 12:08 AM, Willy Tarreau wrote: > On Mon, Oct 05, 2015 at 11:57:08PM +0200, Baptiste wrote: >> Andrew, >> >> My appologies about the proxy_find_by_name function, I was not in the >> right context!!! >> Tested and approved. >> >> Willy, you can apply :)

Re: OPTIM : IPv6 literal address parsing

Hi, On Tue, Oct 06, 2015 at 05:34:07PM +0200, Mildis wrote: > Hi Willy, > > My bad : in the doc, I didn???t get the « add a colon without a port to > end an address » trick. > That???s why I was lost at first. > The doc obviously says ???[:[port]]??? making the port optional > and an ending

Re: Interactive stats socket broken on master

On Fri, Oct 2, 2015 at 10:24 AM, Andrew Hayworth wrote:> > Attached is a patch that fixes the issue for me. Willy, any thoughts on merging this patch into 1.6?

Re: OPTIM : IPv6 literal address parsing

Hi Willy, My bad : in the doc, I didn’t get the « add a colon without a port to end an address » trick. That’s why I was lost at first. The doc obviously says ‘[:[port]]’ making the port optional and an ending colon valid but it looks like a typo to me as ending an IPv6 address with a colon

HTTP Response Rewriting to Replace Internal IP with FQDN

Dear HAProxy Developers, After incorporating insights from Bryan Talbot and articles from Baptiste Assman on HAProxy Web site, we have been able to get the basic configuration of HAProxy going. Now we are adding configuration to access specific products in our LAN. We would like to access

RE: OPTIM : IPv6 literal address parsing

Thanks for your feedback. I think it need improvement as I currently replace the closing bracket with a null directly in the string. Working on a copy and leave the original string as-is should be better. Plus adding some logic here and there to match all cases ... I’ll work on this asap.

Set/add header

Hello, We have Ngnix proxy backend server proxying request for zimbra. We have haproxy servers above the Ngnix proxies. Due some code within zimbra, zimbra is unable to accept set header/ add header from haproxy, so thinking of removing, could you elaborate on how this below line works

Re: core dump, lua service, 1.6-dev6 ss-20150930

Hi Thierry, Op 6-10-2015 om 9:47 schreef Thierry FOURNIER: On Mon, 5 Oct 2015 21:04:08 +0200 PiBa-NL wrote: Hi Thierry, Hi Pieter, With or without "option http-server-close" does not seem to make any difference. Sure, it is only an answer to the Cyril keep alive

Re: OPTIM : IPv6 literal address parsing

On Mon, Oct 05, 2015 at 06:42:52PM +0200, Mildis wrote: > Le 2015-10-05 18:07, David du Colombier a écrit : > >>It looks like IPv6 parsing may lead to errors. > >>The logic cannot distinguish from ???2001:db8::1234:80??? as : > >>- a plain IPv6 address 2001:db8::1234:80 > >>- IPv6 2001:db8::1234

Jusqu'a 80% de reduction sur vos cartouches!

Title: Imprim'Encre Si ce message ne s'affiche pas correctement, lisez-le sur cette page PROFITEZ DE NOTRE OFFRE SPéCIALE RENTREE

Re: core dump, lua service, 1.6-dev6 ss-20150930

On Mon, 5 Oct 2015 21:04:08 +0200 PiBa-NL wrote: > Hi Thierry, Hi Pieter, > With or without "option http-server-close" does not seem to make any > difference. Sure, it is only an answer to the Cyril keep alive problem. I encounter again the keepalive problem :( The

Re: HTTP Response Rewriting to Replace Internal IP with FQDN

On Wed, Oct 7, 2015 at 7:06 AM, Susheel Jalali wrote: > Dear HAProxy Developers, > > After incorporating insights from Bryan Talbot and articles from Baptiste > Assman on HAProxy Web site, we have been able to get the basic > configuration of HAProxy going. Now we

Flight case solution for Kiosk display or Smart TV

Hi there, We are the leading flight case manufacturer especially for Kiosk display/Smart TV products. We have various solutions for the packaging of your fragile display proudcts for transportation. They can be with hidden wheels or removable wheels, also they can afford the weight

[ANNOUNCE] haproxy-1.6-dev7

Hi ladies and gentlemen! Things are calming down when I'm away from the keyboard, I'll start to think I'm really the only one who introduces bugs! Some issues were fixed since dev6 : - segfault recent regression in logs from lua - getaddrinfo() didn't honnor local address selection policy on

Re: [ANNOUNCE] haproxy-1.6-dev7

On 06/10/2015 12:25 μμ, Willy Tarreau wrote: > Hi ladies and gentlemen! > > Things are calming down when I'm away from the keyboard, I'll start to > think I'm really the only one who introduces bugs! > > Some issues were fixed since dev6 : > - segfault recent regression in logs from lua >

FW: HAProxy

Bonjour First of all, if I need to explain in English, please tell me. Je suis bloqué avec HAProxy sur une VM. J'ai un serveur Debian 8.2 avec HAProxy 1.5.14. Et "derrière", j'ai 2 serveurs Windows avec IIS 8.5 & SharePoint 2013. Cela fonctionne bien en HTTP, mais pas en HTTPS. avec HTTPS j'ai

[PATCH] MINOR: lua: fix a spelling error in some error messages

From: Vincent Bernat "unknown" was spelled "unkown". --- src/hlua.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/hlua.c b/src/hlua.c index ae3fe8938f6b..c797d4011129 100644 --- a/src/hlua.c +++ b/src/hlua.c @@ -1261,7 +1261,7 @@ __LJMP

Re: OPTIM : IPv6 literal address parsing

Le 2015-10-06 17:47, Willy Tarreau a écrit : Hi, You must not forbid "[2001:db8::1234]:" otherwise people will not adopt the square brackets notation. Some of them probably already do things like this : server srv1 $IP_SRV1:$PORT_SRV1 And fill the respective environment variables with

Re: OPTIM : IPv6 literal address parsing

On Tue, Oct 06, 2015 at 05:57:09PM +0200, Mildis wrote: > >And regarding "2001:db8::1234", you can't forbit it simply because you > >don't know if 1234 is a port or not in this context, as you have > >reported. > > Sure. In this very specific case 1234 can???t be a port as 2001:db8:: is > then

RE: OPTIM : IPv6 literal address parsing

Hi Mildis, >> And regarding "2001:db8::1234", you can't forbit it simply because you >> don't know if 1234 is a port or not in this context, as you have >> reported. > > Sure. In this very specific case 1234 can’t be a port as 2001:db8:: is > then a subnet. For the record: you can't know that,