Hi again,

It looks like the "option httpclose" is effective, even though the client 
receives a keep-alive header, likely from another intermediate proxy.


>From the HAProxy status page, I can see that the number of concurrent sessions 
>is kept low. And this is really what matters I believe (not to exceed 
>Openshift limits).


/ Mats


Mats wrote:



> Hi Holger,

>

>Many thanks for this hint. I guess I will need to follow up with 
>Openshift/RedHat.

>I have posted a question in the forum there, but so far no feedback: 
>https://stackoverflow.com/questions/44134775/how-to-suppress-http-connection-keep-alive-header-in-response.

>

>Thanks also for the advice to upgrade. I'm not sure if that is easy or even 
>possible in Openshift online. Maybe their next version of the platform (v3) 
>will have a more recent version of >HAProxy. Would be nice, because I am also 
>missing some of the config options that were added in later versions.

>

>Kind regards,

>Mats



>

>
>Hi Mats,
>
>Mats Eklund wrote:
>> I am running a load balanced Tomcat application on Openshift Online
>>v2, with HAProxy ver. 1.4.22 as load balancer.
>
>With your current config, HAProxy will add a "Connection: close" header
>to responses. However, since you mentioned you are running this in an
>OpenShift environment, there might (and probably is)  be another layer
>of proxies involved between your HAProxy and your client.
>
>Since you are speaking plain HTTP here, this other proxy might chose to
>use keep-alive connections towards the client, similar to how HAProxy's
>option http-server-close works. In that case, you would have to change
>the configuration of this other proxy too.
>
>Best,
>Holger
>
>P.S. HAProxy 1.4 is OLD and receives only critical fixes now. You should
>seriously consider upgrading to a newer version. The current stable
>version if 1.7.26.
>
>At the very least, you should upgrade to the latest 1.4 version 1.4.27
>has fixed 83 known bugs since 1.4.22. See
>https://www.haproxy.org/bugs/bugs-1.4.22.html<https://www.haproxy.org/bugs/bugs-1.4.22.html>
> for details.

Reply via email to