LinkedIn
Hi Shaoquan,
İbrahim sent you an invitation to connect. How would you like to respond?
Accept
We are using haproxy with tproxy to front of our various web services.
Most of them are very short lived one-off requests, so we have generally
optimised for closing everything quickly and getting out of the way. We
have a new case where we would like client keep-alives, while maintain
are
If you're asking for keep-alive from client to haproxy and no keep alive
from haproxy to server, then that's what the http-server-close option
provides.
What makes you think that keep alive is not working?
-Bryan
On Wed, Jan 30, 2013 at 6:32 AM, Chris Burroughs
chris.burrou...@gmail.comwrote:
Form curl:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Cache-Control: max-age=72
Content-Type: application/json;charset=UTF-8
Date: Wed, 30 Jan 2013 21:31:14 GMT
Connection: close
* Closing connection #0
as opposed to ending with something like
* Connection #0 to host HOST left intact
with
Oh, your backend looks like it's tomcat? Some tomcat versions mishandle
HTTP 1.1 and keep-alive so the http-pretend-keepalive was added a while ago
to handle servers like that. Does that work better?
-Bryan
On Wed, Jan 30, 2013 at 1:36 PM, Chris Burroughs
chris.burrou...@gmail.comwrote:
I read http://code.google.com/p/haproxy-docs/wiki/http_pretend_keepalive
and it seems to involve stopping haproxy from setting Connection: close
when the server did not. I want the opposite: haproxy to *not* set
Connection:close when the backend does.
Well, funny you should mention tomcat. The
http-pretend-keepalive still enables keep-alive to the client like
http-server-close does.
The difference is that http-server-close sends a Connection: close to the
backend to indicate it doesn't intend to use keep alive. This however
confuses some tomcat versions and causes them to act like the
On Wed, Jan 30, 2013 at 05:16:26PM -0800, Bryan Talbot wrote:
http-pretend-keepalive still enables keep-alive to the client like
http-server-close does.
The difference is that http-server-close sends a Connection: close to the
backend to indicate it doesn't intend to use keep alive. This
Hi Runozo,
On Tue, Jan 29, 2013 at 12:30:37PM +0100, Runozo wrote:
Greeetings and thanks for Haproxy
I have the following backends configured and working with correct ACLs:
backend back1
description balanced server apps
mode http
cookie SRV insert nocache
9 matches
Mail list logo