Re: MEDIUM: Adding upstream socks4 proxy support

2019-06-03 Thread Willy Tarreau
On Mon, Jun 03, 2019 at 07:19:46AM +0200, Willy Tarreau wrote: > On Mon, Jun 03, 2019 at 01:40:28AM +0800, Alec Liu wrote: > > Hi Willy, > > > > Your configuration working for me too, but once I have the "mode tcp" > > changed to "mode http", it was failed. > > Can you give it a try by changing

compression performance drop in v1.9 and v2.0

2019-06-03 Thread flamesea12
Hi I recently found that compression performance drops down after I update to v1.9 I dug a little bit and found that there are many forward calls with a length of zero Breakpoint 1, comp_http_forward_data (s=0x86a620, filter=0x873c70, msg=0x86b960, len=0) at src/flt_http_comp.c:386 which

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
I forgot to notice - haproxy is very close to 2.0 release (about 2 weeks or so). we wish to be sure it works on cygwin before 2.0 released пн, 3 июн. 2019 г. в 13:57, Илья Шипицин : > Hello, Gil Bahat! > > can you help with troubleshooting? > > I created some basic cygwin CI: > >

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
Hello, Gil Bahat! can you help with troubleshooting? I created some basic cygwin CI: https://github.com/chipitsine/haproxy/blob/master/.travis.yml#L25-L30 it fails with src/ev_poll.c:16:10: fatal error: poll.h: No such file or directory #include ^~~~ compilation terminated.

Re: MEDIUM: Adding upstream socks4 proxy support

2019-06-03 Thread Alec Liu
Hi Willy, Totally understand. Thank you for the kindness! Regards, Alexander Liu On Mon, Jun 3, 2019 at 5:39 PM Willy Tarreau wrote: > > On Mon, Jun 03, 2019 at 04:50:57PM +0800, Alec Liu wrote: > > Hi Willy, > > > > Good to know it was fixed. > > I will try to do some more testing as well. >

Re: MEDIUM: Adding upstream socks4 proxy support

2019-06-03 Thread Alec Liu
Hi Willy, Good to know it was fixed. I will try to do some more testing as well. btw: do you mind if I am trying to have the SOCKS4 support backported to 1.9 and 1.8? Thank you. Regards, Alexander Liu On Mon, Jun 3, 2019 at 2:42 PM Willy Tarreau wrote: > > On Mon, Jun 03, 2019 at 07:19:46AM

Re: MEDIUM: Adding upstream socks4 proxy support

2019-06-03 Thread Willy Tarreau
On Mon, Jun 03, 2019 at 04:50:57PM +0800, Alec Liu wrote: > Hi Willy, > > Good to know it was fixed. > I will try to do some more testing as well. OK. > btw: do you mind if I am trying to have the SOCKS4 support backported > to 1.9 and 1.8? We normally don't backport new features into stable

Re: [ANNOUNCE] haproxy-2.0-dev5

2019-06-03 Thread Aleksandar Lazic
Am 02.06.2019 um 13:00 schrieb Willy Tarreau: > Hi, > > HAProxy 2.0-dev5 was released on 2019/06/02. It added 92 new commits > after version 2.0-dev4. > > This version addresses a small number of no-to-trivial issues met while > working on fixing other bugs and during benchmarks. > > One such

Re: [ANNOUNCE] haproxy-2.0-dev5

2019-06-03 Thread Willy Tarreau
Hi Aleks, On Mon, Jun 03, 2019 at 01:42:45PM +0200, Aleksandar Lazic wrote: > Is this test usefull in docker setup? > > ## Starting vtest ## > Testing with haproxy version: 2.0-dev5 > #top TEST reg-tests/seamless-reload/abns_socket.vtc FAILED

Re: cygwin compilation error

2019-06-03 Thread Willy Tarreau
Hi Ilya, On Mon, Jun 03, 2019 at 01:57:48PM +0500, ??? wrote: > Hello, Gil Bahat! > > can you help with troubleshooting? > > I created some basic cygwin CI: > > https://github.com/chipitsine/haproxy/blob/master/.travis.yml#L25-L30 > > it fails with > > src/ev_poll.c:16:10: fatal

Re: cygwin compilation error

2019-06-03 Thread Gil Bahat
poll.h seems to be present at cygwin-devel: https://cygwin.com/cgi-bin2/package-grep.cgi?grep=poll.h=x86_64 hope that helps. Regards, Gil On Mon, Jun 3, 2019 at 5:53 PM Илья Шипицин wrote: > > > пн, 3 июн. 2019 г. в 17:56, Willy Tarreau : > >> Hi Ilya, >> >> On Mon, Jun 03, 2019 at

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
пн, 3 июн. 2019 г. в 20:00, Gil Bahat : > poll.h seems to be present at cygwin-devel: > https://cygwin.com/cgi-bin2/package-grep.cgi?grep=poll.h=x86_64 > > hope that helps. > > cygwin-devel is installed https://travis-ci.com/chipitsine/haproxy/builds/114061737#L165-L172 > Regards, > > Gil >

Re: [ANNOUNCE] haproxy-2.0-dev5

2019-06-03 Thread Илья Шипицин
пн, 3 июн. 2019 г. в 16:56, Willy Tarreau : > Hi Aleks, > > On Mon, Jun 03, 2019 at 01:42:45PM +0200, Aleksandar Lazic wrote: > > Is this test usefull in docker setup? > > > > ## Starting vtest ## > > Testing with haproxy version: 2.0-dev5 > > #

Re: [ANNOUNCE] haproxy-2.0-dev5

2019-06-03 Thread Aleksandar Lazic
Hi Willy. Mon Jun 03 14:05:07 GMT+02:00 2019 Willy Tarreau : > Hi Aleks, > > On Mon, Jun 03, 2019 at 01:42:45PM +0200, Aleksandar Lazic wrote: > > Is this test usefull in docker setup? > > > > ## Starting vtest ## > > Testing with haproxy

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
пн, 3 июн. 2019 г. в 17:56, Willy Tarreau : > Hi Ilya, > > On Mon, Jun 03, 2019 at 01:57:48PM +0500, ??? wrote: > > Hello, Gil Bahat! > > > > can you help with troubleshooting? > > > > I created some basic cygwin CI: > > > >

Re: Lua logging to syslog & not stderr

2019-06-03 Thread Willy Tarreau
Hi Patrick, On Mon, Jun 03, 2019 at 11:51:12AM -0400, Patrick Hemmer wrote: > Is there a way to have Lua log to syslog only, and not to stderr? When I > call `TXN.log(...)`, the message shows up in syslog AND stderr. > > The Lua documentation implies this is possible as it has this statement >

Lua logging to syslog & not stderr

2019-06-03 Thread Patrick Hemmer
Is there a way to have Lua log to syslog only, and not to stderr? When I call `TXN.log(...)`, the message shows up in syslog AND stderr. The Lua documentation implies this is possible as it has this statement (http://www.arpalert.org/src/haproxy-lua-api/1.9/index.html): > The log is sent,

Re: compression performance drop in v1.9 and v2.0

2019-06-03 Thread Willy Tarreau
Hi, On Mon, Jun 03, 2019 at 06:06:02PM +0900, flamese...@yahoo.co.jp wrote: > I recently found that compression performance drops down after I update to > v1.9 > > I dug a little bit and found that there are many forward calls with a length > of zero > > Breakpoint 1, comp_http_forward_data

unset-var doesn't support conditions

2019-06-03 Thread Patrick Hemmer
It appears that all usages of unset-var don't support conditions. Meaning none of the following work: http-request unset-var(txn.foo) if { always_true } tcp-request content unset-var(txn.foo) if { always_true } etc. The error presented is: [ALERT] 153/175307 (58641) : parsing

cygwin build error

2019-06-03 Thread Илья Шипицин
Hello, I'm trying yo build haproxy (git master) on cygwin. $ make CC=gcc V=1 TARGET=cygwin FLAGS= ... src/mux_h2.o: In function `h2s_frt_make_resp_data': /home/chipitsine/haproxy/src/mux_h2.c:4405: undefined reference to `trace' /home/chipitsine/haproxy/src/mux_h2.c:4405:(.text+0xce79):

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
btw, Bob, can you run reg-tests on cygwin ? maybe you can prepare travis-ci config for cygwin ? вт, 4 июн. 2019 г. в 00:57, Zakharychev, Bob : > Ilya, > > > > FWIW: I tried to build 2.0-dev5 on my working copy of Cygwin-64 3.0.7 with > GCC toolchain 8.3.0 running just > > > > make TARGET=cygwin

RE: cygwin compilation error

2019-06-03 Thread Zakharychev, Bob
Ilya, Try pulling in gcc-core libgcc1 binutils. I can’t actually see how it’s compiling without a compiler :), but worth trying. Also, check output from cpp -v /dev/null -o /dev/null This should print the search path – we can then verify that /usr/include and other dirs are in it. Bob From:

http_first_req not working with http2

2019-06-03 Thread Patrick Hemmer
As subject says, it appears that the http_first_req sample is not working with http2. Config:   frontend f1     bind :8000     option http-use-htx     log-format http_first_req=%[http_first_req] With `curl http://localhost:8000` Outputs:   <30>Jun  3 17:16:36 haproxy[47767]: http_first_req=1

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
вт, 4 июн. 2019 г. в 01:23, Zakharychev, Bob : > Ilya, > > > > Try pulling in gcc-core libgcc1 binutils. I can’t actually see how it’s > compiling without a compiler :), but worth trying. Also, check output from > it had picked gcc from windows :) installing "gcc-core" resolved that > > cpp

Re: cygwin compilation error

2019-06-03 Thread Илья Шипицин
вт, 4 июн. 2019 г. в 00:57, Zakharychev, Bob : > Ilya, > > > > FWIW: I tried to build 2.0-dev5 on my working copy of Cygwin-64 3.0.7 with > GCC toolchain 8.3.0 running just > > > > make TARGET=cygwin > > > > and it compiled successfully, but initially didn’t link due to > > > > src/mux_h2.o: In

RE: cygwin compilation error

2019-06-03 Thread Zakharychev, Bob
Ilya, FWIW: I tried to build 2.0-dev5 on my working copy of Cygwin-64 3.0.7 with GCC toolchain 8.3.0 running just make TARGET=cygwin and it compiled successfully, but initially didn’t link due to src/mux_h2.o: In function `h2s_frt_make_resp_data': /build/haproxy-2.0-dev5/src/mux_h2.c:4405:

Re: http_first_req not working with http2

2019-06-03 Thread Patrick Hemmer
*From:* Patrick Hemmer [mailto:hapr...@stormcloud9.net] *Sent:* Monday, June 3, 2019, 17:21 EDT *To:* haproxy@formilux.org *Subject:* http_first_req not working with http2 As subject says, it appears that the

segfault in tcp-request session set-var

2019-06-03 Thread Patrick Hemmer
In haproxy 1.9.8, if you do `tcp-request session set-var()` with a variable in any scope other than sess, it segfaults. For example: tcp-request session set-var(txn.foo) ... tcp-request session set-var(req.foo) ... * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS

Re: SD-termination cause

2019-06-03 Thread Максим Куприянов
Hi Willy! Sorry for bothering you, but do you have any news about this case? чт, 23 мая 2019 г. в 10:35, Willy Tarreau : > Hi Maksim, > > On Thu, May 23, 2019 at 10:00:19AM +0300, ?? ? wrote: > > 2nd session (from haproxy to ssl-enabled backend A, dumped with tshark > for > > better