Hi Aman,
On Mon, Apr 02, 2012 at 03:34:08PM -0700, Aman Gupta wrote:
OK just to be sure, you should *really* make your changes on 1.5-dev, not
1.4. 1.4 is in deep maintenance mode and I don't intend to merge such
changes there, as every time I did I caused some regressions.
I'm in
On Mon, Apr 2, 2012 at 11:21 PM, Willy Tarreau w...@1wt.eu wrote:
Hi Aman,
On Mon, Apr 02, 2012 at 03:34:08PM -0700, Aman Gupta wrote:
OK just to be sure, you should *really* make your changes on 1.5-dev, not
1.4. 1.4 is in deep maintenance mode and I don't intend to merge such
changes
On Tue, Apr 3, 2012 at 12:10 AM, Brane F. Gračnar
brane.grac...@tsmedia.si wrote:
On 04/03/2012 08:21 AM, Willy Tarreau wrote:
The protocol is described here :
http://haproxy.1wt.eu/download/1.5/doc/proxy-protocol.txt
Please let me know whether you're interested, then I'll check where
OK just to be sure, you should *really* make your changes on 1.5-dev, not
1.4. 1.4 is in deep maintenance mode and I don't intend to merge such
changes there, as every time I did I caused some regressions.
I'm in process of porting my patch to 1.5. I don't particularly want
to run 1.5 in
On 03/25/2012 07:55 AM, Aman Gupta wrote:
A 1 127.0.0.1:50869 - 127.0.0.1:9418
F 1 127.0.0.1:50869 - 127.0.0.1:9418 | 127.0.0.1:50870 - 127.0.0.1:6000
C 1 127.0.0.1:50869 - 127.0.0.1:9418
Is it possible to use [IP]:port format? We're already living in IPv6
world...
Best regards,
On Mon, Mar 26, 2012 at 11:57:01AM +0200, Brane F. Gra??nar wrote:
On 03/25/2012 07:55 AM, Aman Gupta wrote:
A 1 127.0.0.1:50869 - 127.0.0.1:9418
F 1 127.0.0.1:50869 - 127.0.0.1:9418 | 127.0.0.1:50870 - 127.0.0.1:6000
C 1 127.0.0.1:50869 - 127.0.0.1:9418
Is it possible to use
Hi Aman,
On Sat, Mar 24, 2012 at 10:55:50PM -0700, Aman Gupta wrote:
Agreed. For this reason we've recently extended the log format to optionally
include new fields such as the outgoing source IP:port. I would not have
expected another request to come that soon :-)
Quite the coincidence.
Hi Aman,
On Fri, Mar 23, 2012 at 01:33:30PM -0700, Aman Gupta wrote:
Tracing TCP connections that make hops through haproxy is currently very
challenging. To get a list of proxied connection pairs inside haproxy,
one must use `show sess` to dump the session table, grab the fd pairs
for each
Agreed. For this reason we've recently extended the log format to optionally
include new fields such as the outgoing source IP:port. I would not have
expected another request to come that soon :-)
Quite the coincidence. I was working in a haproxy-1.4 checkout, so I
missed the new logging
Tracing TCP connections that make hops through haproxy is currently very
challenging. To get a list of proxied connection pairs inside haproxy,
one must use `show sess` to dump the session table, grab the fd pairs
for each session, resolve those to inodes via the process's file
descriptor table,
10 matches
Mail list logo