Re: healthchecks (to uwsgi) possible regression 1.9.8 -> 1.9.9

2019-10-03 Thread Willy Tarreau
Hi Jarno, On Wed, Oct 02, 2019 at 01:08:14PM +0300, Jarno Huuskonen wrote: > Hello, > > I was testing haproxy -> uwsgi(alert.io) and noticed a possible regression > with healthchecks(httpchk). > With 1.9.9 uwsgi logs: > [uwsgi-http key: host.name.fi client_addr: 127.0.0.1 client_port: 45715] >

Re: Handling Idle clients without specifying timeouts

2019-10-03 Thread Willy Tarreau
Hi, On Thu, Oct 03, 2019 at 06:40:08PM -0700, Shishir Kumar Yadav wrote: > Hi All, > > We are using Haproxy 1.8.3 and have a peculiar situation. We want to remove > idle client connections but without specifying HAProxy timeout, basically > we want to rely on backend to detect whether client is

Handling Idle clients without specifying timeouts

2019-10-03 Thread Shishir Kumar Yadav
Hi All, We are using Haproxy 1.8.3 and have a peculiar situation. We want to remove idle client connections but without specifying HAProxy timeout, basically we want to rely on backend to detect whether client is idle or not because sometimes backend might not be able to send any data on a

Re: Use haproxy behind Squid

2019-10-03 Thread Aleksandar Lazic
Hi Nikita. Am 03.10.19 um 12:02 schrieb Akhnin Nikita: > Hello, Aleksandar! > > Vice versa, actually: Client -> Haproxy -> Squid -> Internet > > Here's the situation. Haproxy instance stands in a private network and > interacts with the Internet through Firewall that performs NAT. Current >

RE: Use haproxy behind Squid

2019-10-03 Thread Akhnin Nikita
Hello, Aleksandar! Vice versa, actually: Client -> Haproxy -> Squid -> Internet Here's the situation. Haproxy instance stands in a private network and interacts with the Internet through Firewall that performs NAT. Current schema looks like this: Client -> Haproxy -> FW (SNAT) -> Internet The