RE: SIGUSR1 soft stop does not send "Connection: close"

Hi, >> If the session is transferring HTTP body between client and backend server, >> we >> can't insert HTTP headers either. If you are waiting for the next request >> in that particular session, why wouldn't we just close it after the HTTP body >> has been transfered? > > That would be fine,

Re: SIGUSR1 soft stop does not send "Connection: close"

On Thu, Oct 15, 2015 at 2:11 PM, Lukas Tribus wrote: > When specifically would you intervene? Could you elaborate what you > have in mind? My goal is to shutdown a HAProxy daemon without interrupting any inflight requests or responses. > If the session is transferring HTTP

RE: SIGUSR1 soft stop does not send "Connection: close"

> From my reading of the code SIGUSR1 does not send a "Connection: close" to the > client or server. This means it is not possible to safely close a keep-alive > session, before terminating HAProxy. > > Would there be interest in a patch to send "Connection: close" on both the > request and the

Re: SIGUSR1 soft stop does not send "Connection: close"

On Thu, Oct 15, 2015 at 12:26 PM, Lukas Tribus wrote: > What request/response, aren't we talking about an idle session here? No, I am concerned with a non idle persistent session.

RE: SIGUSR1 soft stop does not send "Connection: close"

> On Thu, Oct 15, 2015 at 12:26 PM, Lukas Tribus wrote: >> What request/response, aren't we talking about an idle session here? > > No, I am concerned with a non idle persistent session. When specifically would you intervene? Could you elaborate what you have in mind? If