Re: REg: Connection field in HTTP header is set to close while sending to backend server

Hi Lukas, Thank you for the response. Yes, It is new deployment. I will check 1.5. Regards, Ilan On Fri, Aug 7, 2015 at 6:42 PM, Lukas Tribus luky...@hotmail.com wrote: Hi Baptiste, Thank you very much for the response.That was quick. I tired enabling but got following error, Looks

RE: REg: Connection field in HTTP header is set to close while sending to backend server

Hi Baptiste, Thank you very much for the response.That was quick. I tired enabling but got following error,  Looks like you're on haproxy 1.4. In your current configuration you are now using tunnel-mode. If this is a new deployment, I would recommend upgrading to haproxy 1.5. Regards,

REg: Connection field in HTTP header is set to close while sending to backend server

Hi Support, I configured haproxy to forward request to backend server. I did packet capture between browser and haproxy and noticed that connection field in HTTP header is set to keep-alive. Then I did packet capture between haproxy and backend server, I noticed that connection field in HTTP

Re: REg: Connection field in HTTP header is set to close while sending to backend server

Hi Baptiste, Thank you very much for the response.That was quick. I tired enabling but got following error, [ALERT] 218/182924 (17467) : parsing [/etc/haproxy/haproxy.cfg:13] : unknown option 'http-keep-alive'. [ALERT] 218/182924 (17467) : parsing [/etc/haproxy/haproxy.cfg:14] : unknown option

Re: REg: Connection field in HTTP header is set to close while sending to backend server

On Fri, Aug 7, 2015 at 1:25 PM, ilan ilan@gmail.com wrote: Hi Support, I configured haproxy to forward request to backend server. I did packet capture between browser and haproxy and noticed that connection field in HTTP header is set to keep-alive. Then I did packet capture between