Re: HTTP redirects while still allowing keep-alive

Hi all, Le 10/01/2017 à 01:28, Bryan Talbot a écrit : On Jan 8, 2017, at Jan 8, 2:03 PM, Ciprian Dorin Craciun wrote: Quick question: how can I configure HAProxy to redirect (via `http-request redirect ...`) without HAProxy sending the `Connection: close`

Re: HTTP redirects while still allowing keep-alive

> On Jan 8, 2017, at Jan 8, 2:03 PM, Ciprian Dorin Craciun > wrote: > > Quick question: how can I configure HAProxy to redirect (via > `http-request redirect ...`) without HAProxy sending the `Connection: > close` header, thus still allowing keep-alive on this

Re: HAProxy Lua Map.end & reserved keywords

On Mon, Jan 09, 2017 at 07:49:40PM +0100, thierry.fourn...@arpalert.org wrote: > > I see two potential ways forward: > > a) Map['end'] # works right now, but ugly > > b) Map.match_end # intent is much clearer > Hi, thank for you comment ! You're absolutely right. This keyword > doesn't run because

Re: HAProxy Lua Map.end & reserved keywords

On Mon, 9 Jan 2017 18:22:56 + "Robin H. Johnson" wrote: > TL;DR: > 'end' is a reserved Lua keyword, and cannot be used as a structure > member as in Map.end. Need to change the naming of constants maybe? > >

HAProxy Lua Map.end & reserved keywords

TL;DR: 'end' is a reserved Lua keyword, and cannot be used as a structure member as in Map.end. Need to change the naming of constants maybe? http://www.arpalert.org/src/haproxy-lua-api/1.7/index.html#map-class > -- Create and load map > geo = Map.new("geo.map", Map.ip); Now if you want to use

Hadoop users list

Hello there, Might want to know whether you are keen on obtaining Hadoop Leads for your marketing effort? Please review and let me know your thoughts I will get back to you with a more information and Price List. Regards, Michael Talbert

Re: [PATCH 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

No problem I'll have another look tomorrow morning and I'll let you all know how I get on. On 9 January 2017 at 15:18, Simon Horman wrote: > Hi Scott, > > thanks for testing. > > For reference the code I am using is here: > > https://github.com/horms/haproxy.git show-json > >

Re: [PATCH 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

Hi Scott, On Mon, Jan 09, 2017 at 03:10:10PM +, Scott McKeown wrote: > Hi Everyone, > > Simon I've been playing with this patch today and I'm sorry to say that > adding it to a 1.8 dev build as of today does not look to work. > > I did have to manually update a few of the patch chunks so

Re: [PATCH 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

Hi Scott, thanks for testing. For reference the code I am using is here: https://github.com/horms/haproxy.git show-json And my minimal config file is as follows. Would it be possible for you to share you config with me (privately) ? global daemon stats socket /tmp/haproxy.stat

Re: [PATCH 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

Hi Everyone, Simon I've been playing with this patch today and I'm sorry to say that adding it to a 1.8 dev build as of today does not look to work. I did have to manually update a few of the patch chunks so I'm willing to admit that it could be me that broke it and I will be having another go

Re: SCT TLS extensions with 2 certificates

2017-01-09 14:01 GMT+01:00 Pier Carlo Chiodi : > I'm having an issue while trying to serve SCT TLS extensions in a 2 > certificates scenario. This might be a problem with OpenSSL 1.1.0 and SNI. There is a very similar issue reported for nginx CT module

SCT TLS extensions with 2 certificates

I'm having an issue while trying to serve SCT TLS extensions in a 2 certificates scenario. I'm using HA-Proxy version 1.7.1 with static OpenSSL 1.1.0c. Certificates: file www.domain.tld.pem - Subject: CN=domain.tld - Subject Alternative Name: DNS:domain.tld, DNS:www.domain.tld file

Add agent-host configuration directive and allow changing it and agent-send via socket/CLI

Hello! It's my first PR to haproxy, so please tell me if anything still wrong. I've read CONTRIBUTING. This patches implements possiblity to define different host (agent-host) for agent checks in config and they also allow changing agent-host and agent-send variables via CLI/socket. We wonna use

500 Server Error vs. 500 Internal Server Error ?

Hello, Haproxy uses 500 "Server Error" for error/status code 500. AFAIK RFC 2616/7231 and most? other servers use 500 "Internal Server Error". Is there a reason for using "Server Error" and not "Internal Server Error" ? If you think "Internal Server Error" is more suitable then this patch