RE: HAProxy Build Error with TARGET

2016-09-13 Thread Coscend@HAProxy
Bryan, Thank you for your prompt guidance. We downloaded this source code: http://www.haproxy.org/download/1.6/src/haproxy-1.6.9.tar.gz After reviewing your e-mail, we found out (from https://github.com/haproxy/haproxy) that we should use TARGET=linux2628 "- linux2628 for Linux

Re: HAProxy Build Error with TARGET

2016-09-13 Thread Bryan Talbot
> On Sep 13, 2016, at Sep 13, 9:16 PM, Coscend@HAProxy > wrote: > > Hello HAProxy Community, > > We are upgrading from HAProxy 1.6.7 to 1.6.9 by building from source. We > would appreciate any vector on the issue we are facing with specifying > TARGET in make

HAProxy Build Error with TARGET

2016-09-13 Thread Coscend@HAProxy
Hello HAProxy Community, We are upgrading from HAProxy 1.6.7 to 1.6.9 by building from source. We would appreciate any vector on the issue we are facing with specifying TARGET in make and makefile. It is building fine with TARGET=linux2628. However, we are getting a build error with

Re: Capture entire HTTP request (all headers one shot)

2016-09-13 Thread Manas Gupta
Thanks for the pointer. I need to log the values of these headers as well. Any suggestions on how to do that? On Tue, Sep 13, 2016 at 1:28 PM, Pavlos Parissis wrote: > On 13/09/2016 09:58 μμ, Manas Gupta wrote: > > Hi, > > I am familiar with capturing individual HTTP

Re: Capture entire HTTP request (all headers one shot)

2016-09-13 Thread Pavlos Parissis
On 13/09/2016 09:58 μμ, Manas Gupta wrote: > Hi, > I am familiar with capturing individual HTTP headers in HAProxy 1.6.x > (http://blog.haproxy.com/2015/10/14/whats-new-in-haproxy-1-6/). This requires > the > header to be explicitly stated in the cfg > > For example to capture the via header - >

Capture entire HTTP request (all headers one shot)

2016-09-13 Thread Manas Gupta
Hi, I am familiar with capturing individual HTTP headers in HAProxy 1.6.x ( http://blog.haproxy.com/2015/10/14/whats-new-in-haproxy-1-6/). This requires the header to be explicitly stated in the cfg For example to capture the via header - capture request header Via len 100 And then log via -

化工品国际快递无需提供任何资料

2016-09-13 Thread mr zhang
您好：首先对我们的冒昧来访深表歉意。希望我们的信息能给你带来帮助。我这边是茹顺化工科技国际快递，专注农药产品登记，化工产品登记，贸易产品 大包小包　 解决疑难杂症产品出口的国际快递，价格优惠，无需提供任何资料及DGM鉴定报告，空运鉴定报告。 承接类型：电池 化工品 液体 粉末 颗粒颜料电池等等疑难产品。电话：158.0058918.0 QQ：1163.07587.8 张经理 欢迎来电咨询

Re: [PATCH] MINOR: enable IP_BIND_ADDRESS_NO_PORT on backend connections

2016-09-13 Thread Willy Tarreau
On Tue, Sep 13, 2016 at 09:51:15AM +, Lukas Tribus wrote: > Enable IP_BIND_ADDRESS_NO_PORT on backend connections when the source > address is specified without port or port ranges. This is supported > since Linux 4.2/libc 2.23. > > If the kernel supports it but the libc doesn't, we can

[PATCH] MINOR: enable IP_BIND_ADDRESS_NO_PORT on backend connections

2016-09-13 Thread Lukas Tribus
Enable IP_BIND_ADDRESS_NO_PORT on backend connections when the source address is specified without port or port ranges. This is supported since Linux 4.2/libc 2.23. If the kernel supports it but the libc doesn't, we can define it at build time: make [...] DEFINE=-DIP_BIND_ADDRESS_NO_PORT=24 For

Re: [PATCH 2/3] MINOR: show Built with PCRE version

2016-09-13 Thread Willy Tarreau
Hi Lukas, On Mon, Sep 12, 2016 at 09:38:20PM +, Lukas Tribus wrote: > The 4th (new) patch that I'm sending implements the possibility to > disable SO_REUSEPORT. The intention with that patch is to have it > backported to 1.6 in the long run, because I believe it is useful not > only for