Hi Thomas,

Should be complicated to see it with netstat!
Better use wireshark/tcpdump or HAProxy logs and counting the number
of requests per IP/port source.

Baptiste

On Mon, Jan 6, 2014 at 5:03 PM, Thomas Sheppard
<[email protected]> wrote:
> Hi Baptiste
>
> That is what I thought however shouldn't it be sending the keep alive header
> in order to conform with 1.0?
>
> Also it doesn't seem any of the connections are kept alive anyway.
>
> If I run -  ab -kc 1000 -n 10000 https://ipaddress against the HAProxy
> server.
>
> The netstat -o on the server running HAProxy shows Time-Wait instead of
> Keep-Alive. I'm just unconvinced the connection is being kept alive as
> expected.
>
> Kind regards,
>
> Thomas
>
>
>
> On Mon, Jan 6, 2014 at 3:55 PM, Baptiste <[email protected]> wrote:
>>
>> Hi Thomas,
>>
>> in HTTP 1.1, keepalive is implicit:
>> http://tools.ietf.org/html/rfc2616#section-8.1.2
>>
>> Baptiste
>>
>> On Mon, Jan 6, 2014 at 3:21 PM, Thomas Sheppard
>> <[email protected]> wrote:
>> > Hi Everyone,
>> >
>> > We are running HAProxy V1.5 as described in the subject. I am trying to
>> > enable Keep-Alive and have noticed the response headers do not contain
>> > the
>> > Connection: Keep-Alive header.
>> >
>> > Our haproxy.cfg contains the following defaults which I believe should
>> > enable keep alive:
>> >
>> >     mode http
>> >     timeout connect 15000ms
>> >     timeout client 50000ms
>> >     timeout server 30000ms
>> >     timeout http-keep-alive 10s
>> >     option http-keep-alive
>> >
>> > I notice if I get rid of option http-keep-alive then the Connection:
>> > Close
>> > response header is being returned. Can anyone tell me is HAProxy not
>> > returning the Keep-Alive header as it's technically not requires in http
>> > 1.1
>> > forward or is it that HAProxy simply isn't enabling Keep-Alive.
>> >
>> > If it is the latter can anyone tell me why it wouldn't be working?
>> >
>> > A little more info from our config below
>> >
>> > frontend server_Frontend
>> >
>> >   mode http
>> >   rspidel ^Server
>> >   rspidel ^Date
>> >   rspidel ^Vary
>> >   rspidel ^Content-Type
>> >
>> >   bind 0.0.0.0:443 ssl crt //home/ubuntu/certs/cert.pem
>> >
>> >   default_backend server_Backend
>> >
>> > backend server_Backend
>> > mode http
>> > balance roundrobin
>> > server srv1 x.y.Z.1:80 maxconn 50 check
>> >
>> > Thanks for any help.
>
>

Reply via email to