Re: missing sessions from show sess

2021-07-18 Thread Joao Morais


> Em 16 de jul. de 2021, à(s) 22:16, Joao Morais  
> escreveu:
> 
> ...
> 
> # show sess
> 
>$ awk '{print $4}' sess |sort |uniq -c
>  1
>  1 fe=GLOBAL
>   1902 fe=_front__tls
>  2 fe=_front_http
> 38 fe=_front_https
> 
> ...
> 
> The third output shows the number of current sessions per frontend, 
> _front__tls seems to be correct, however http and https are apparently 
> missing lots of sessions. Shouldn’t the other frontends have a similar number 
> of sessions compared with their show stat counterpart? Is there a way to find 
> and list the remaining http and https connections?


Now  I think I can answer myself, after a few tests on a local environment, 
maybe this can be useful for someone in the future having the same doubts 
(including me).

_front__tls is a mode tcp proxy, so the number of active sessions, listed by 
show sess, will be the same the number of connections to that frontend.

_front_http and _front_https are mode http proxies, so the number of active 
sessions, listed by show sess, will be the number of running http requests. As 
soon as the http request finishes, the session disappear from the list, event 
though the client is still connected to the frontend - global ConnCurrs counts 
this.

The difference between global ConnCurrs (show info) or scur (show stat) and the 
list above (show sess) is apparently the active connections, counting in show 
info and show stat, without a running http request or a http tunnel (eg 
websocket), so without counting in show sess. If my assumption is correct, "  
4. scur [LFBS]: current sessions" from the management guide could be clarified 
on how it works on mode http frontends.

~jm




Re: set mss on backend site on version 1.7.9

2021-07-18 Thread Willy Tarreau
On Thu, Jul 15, 2021 at 07:04:27PM +0200, Stefan Fuhrmann wrote:
> Hello Lukas,
> 
> 
> okay, thanks!!

By the way, I think we never implemented it because it didn't appear
useful. Out of curiosity, what is your use case ? If really useful, I
think it shouldn't be too hard to implement.

Willy



[PR] a fix patch for issue#1326

2021-07-18 Thread PR Bot
Dear list!

Author: jenny-cheung 
Number of patches: 1

This is an automated relay of the Github pull request:
   a fix patch for issue#1326

Patch title(s): 
   a fix patch for issue#1326

Link:
   https://github.com/haproxy/haproxy/pull/1329

Edit locally:
   wget https://github.com/haproxy/haproxy/pull/1329.patch && vi 1329.patch

Apply locally:
   curl https://github.com/haproxy/haproxy/pull/1329.patch | git am -

Description:
   a fix patch for issue#1326. Thank you for the checking.

Instructions:
   This github pull request will be closed automatically; patch should be
   reviewed on the haproxy mailing list (haproxy@formilux.org). Everyone is
   invited to comment, even the patch's author. Please keep the author and
   list CCed in replies. Please note that in absence of any response this
   pull request will be lost.