Re: fields vs word converter, unexpected "0" result

Hi, Le 01/08/2017 à 17:37, Daniel Schneller a écrit : Any idea on the difference between “word” and “field”, though? "field" and "word" are similar, except that "word" will ignore consecutive delimiters without any word. Example with "x//y/z" : word(1,/) => returns "x" word(2,/) =>

Re: fields vs word converter, unexpected "0" result

On 1. Aug. 2017, at 17:32, Holger Just wrote: > GET / HTTP/1.1 > Host: 127.0.0.1:8881 > User-Agent: curl/7.43.0 > Accept: */* > > The HTTP 1.1 specification requires that a Host header is always sent > along with the request. Curl specifically always sends the host from the

Re: fields vs word converter, unexpected "0" result

Hi Daniel, Daniel Schneller wrote: > root@haproxy-1:~# curl -s http://127.0.0.1:8881 > Aug 1 15:12:55 haproxy-1 haproxy[3049]: 127.0.0.1:45875 > [01/Aug/2017:15:12:55.198] "0" > > While the first three are expected, the last one confuses me. Why would > leaving the header out result in “0”

fields vs word converter, unexpected "0" result

Hi! First, the basics: -- root@haproxy-1:~# haproxy -vv HA-Proxy version 1.6.13-1ppa1~trusty 2017/06/19 Copyright 2000-2017 Willy Tarreau Build options : TARGET = linux2628 CPU = generic CC = gcc CFLAGS = -g -O2 -fPIE -fstack-protector

Re: PIDs are not dying on a reload

❦ 1 août 2017 12:00 +0200, "Arnaud B."  : > I'm not using peers, it's a feature that I've discovered as you > mentionned it, seems worth the try. > > I'll upgrade to the latest bpo package from Vincent's repository and see > if it fixes my issue, I'll get back to you if it

Re: PIDs are not dying on a reload

I'm not using peers, it's a feature that I've discovered as you mentionned it, seems worth the try. I'll upgrade to the latest bpo package from Vincent's repository and see if it fixes my issue, I'll get back to you if it succeeds or not. Thank's Will. Le 01/08/2017 à 11:32, Willy Tarreau a

Re: Lua + shared memory segment

2017-08-01 10:47 GMT+02:00 Thierry Fournier : > >> On 31 Jul 2017, at 22:41, bjun...@gmail.com wrote: >> >> Hi, >> >> i'm experimenting with some Lua code in HAProxy where i need a simple >> key/value store (not persistent). I want to avoid Redis or other external

Re: PIDs are not dying on a reload

On Tue, Aug 01, 2017 at 10:49:20AM +0200, Arnaud B. wrote: > thank's Vincent. > > Unfortunately, I already am on the latest upstream (not backport though) : > > $ apt-get update -qq; apt-cache madison haproxy; dpkg -l|grep -i haproxy >haproxy | 1.7.8-1~bpo9+1 |

Re: PIDs are not dying on a reload

❦ 1 août 2017 10:49 +0200, "Arnaud B."  : > thank's Vincent. > > Unfortunately, I already am on the latest upstream (not backport though) : > > $ apt-get update -qq; apt-cache madison haproxy; dpkg -l|grep -i haproxy >haproxy | 1.7.8-1~bpo9+1 |

Haproxy POC for oracle apps r12.1.3 ( please help)

Dear Support Team, We are looking for the load balancer for oracle apps r12.1.3. we need POC for Haproxy if you have any doc for the load balancing for oracle apps with 2 node please share. Regards, Arif M. Rangrej

Re: Lua core.(m)sleep + http-response

Thanks for the information. I will check this. > On 31 Jul 2017, at 21:31, bjun...@gmail.com wrote: > > Hi, > > i've an issue that was already posted some time ago (i'm using HAProxy 1.7.8): > > https://discourse.haproxy.org/t/core-msleep-not-working-in-http-resp-http-response > >

Re: PIDs are not dying on a reload

❦ 31 juillet 2017 13:58 +0200, "Arnaud B."  : > I changed my haproxy.cfg to use only the haproxy user instead of > www-data, but it haven't fixed my undying pid issue, I have the exact > same stale processes, with a UDP UNCON socket open, no trafic and the > epoll_wait() on

server ports - server state file

Hello Haproxy ML, Here is a simple patch to add server ports to server state file. Regards, Fred. >From eff80e502338618ea991ecb0fac11fd25dec19b2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20L=C3=A9caille?= Date: Tue, 1 Aug 2017 08:47:19 +0200 Subject:

Re: How does HAProxy work internally in terms of http data flow?

Hi, This statement is true by default: > Or maybe haproxy first get all HTTP request header from client, then apply > these filters then forward every bits of http request body to backend, and > forward anything sent by backend to client? > > Then you can enable "option http-buffer-request"