# Current Session in HAProxy stats

**URL:** <https://discourse.haproxy.org/t/current-session-in-haproxy-stats/1331>\
**Category:** Help!\
**Created:** [June 17, 2017, 7:56am UTC](https://discourse.haproxy.org/t/current-session-in-haproxy-stats/1331 "2017-06-17T07:56:54Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dvelan](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@dvelan](https://discourse.haproxy.org/u/dvelan)\
**Post date:** [June 17, 2017, 7:56am UTC](https://discourse.haproxy.org/t/current-session-in-haproxy-stats/1331/1 "2017-06-17T07:56:54Z")

</div>

I have enabled stats for gui, checking session for front-end, the count of “curr session” is always high. Meaning when I just use a single website URL([http://haproxywebserver](http://haproxywebserver): haproxy listen port/shprd/signon.html)from IE browser , instead of displaying 1, it display 5

Any reason? I am using mode http.  
Due to that, I am unable to get the correct count of HTTP connections from different user machine and browser.

Am I missing any configuration?

Haproxy 1.6.12  
RHEL 7.2  
Weblogic 12c back-end

Regards,  
Vel

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [June 17, 2017, 8:52am UTC](https://discourse.haproxy.org/t/current-session-in-haproxy-stats/1331/2 "2017-06-17T08:52:32Z")

</div>

TCPdump it, check what actually happens.  
Or, make a single call with curl, where you know how the client behaves.

A browser may open multiple concurrent sessions.

---

<div class="post-metadata">

**Author:** ![dvelan](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@dvelan](https://discourse.haproxy.org/u/dvelan)\
**Post date:** [June 17, 2017, 9:26am UTC](https://discourse.haproxy.org/t/current-session-in-haproxy-stats/1331/3 "2017-06-17T09:26:30Z")

</div>

Thanks much for your response, I will check on this and revert.  
I also have another query on the same topic, when sign out occurs (cookie will become invalid when sign out occurs) from application, log out URL will be something /?cmd=logout .

Even when session/connection is logged out, the current session, still shows as 1, when I close the browser completely, then curr session becomes 0.

Is there any timeout parameter for the URL having log out string, so that I can force haproxy to release the http connection having logout in the URL without need to close the browser.

Regards,  
Vel

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [June 18, 2017, 8:18pm UTC](https://discourse.haproxy.org/t/current-session-in-haproxy-stats/1331/4 "2017-06-18T20:18:38Z")

</div>

Its simply keep-alive mechanics.

Configure timeout http-keep-alive to adjust this:  
[https://cbonte.github.io/haproxy-dconv/1.7/configuration.html#4-timeout%20http-keep-alive](https://cbonte.github.io/haproxy-dconv/1.7/configuration.html#4-timeout%20http-keep-alive)

---

<div class="post-metadata">

**Author:** ![dvelan](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@dvelan](https://discourse.haproxy.org/u/dvelan)\
**Post date:** [June 19, 2017, 2:58pm UTC](https://discourse.haproxy.org/t/current-session-in-haproxy-stats/1331/5 "2017-06-19T14:58:05Z")

</div>

Thanks Much for your assistance.

Is HAProxy 1.7 stable version to work with RHEL 7.2(3.2)? The readme from 1.7 says it’s a development version.

Currently, I am using 1.6.12, do you think any major enhancement and bug fixes in 1.7. Please advise me.

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [June 19, 2017, 3:51pm UTC](https://discourse.haproxy.org/t/current-session-in-haproxy-stats/1331/6 "2017-06-19T15:51:22Z")

</div>

The directive is in 1.6 as well:  
[https://cbonte.github.io/haproxy-dconv/1.6/configuration.html#4-timeout%20http-keep-alive](https://cbonte.github.io/haproxy-dconv/1.6/configuration.html#4-timeout%20http-keep-alive)

1.7 is not a development version, its perfectly stable.