On Thu, May 09, 2013 at 03:14:13AM +0900, Seri wrote: > Hi, > > In Haproxy SSL and HTTP KeepAlive environment, > After keepalive timeout, haproxy sends FIN to client, but Client(Windows IE > or Chrome) doesn't send ACK to haproxy server. > > So, haproxy server left TCP FIN_WAIT2 state and client left CLOSE_WAIT state.
So this means you have a bug on the client which didn't notice the FIN. It's possible it was doing something else and not monitoring the connection state, and will notice it once it needs to perform another request. Anyway I find this dirty. > How this issue will be solved? Only on the client. Don't worry, this is harmless. FIN_WAIT2 connections don't last long, so even if a firewall in the middle expires its session, the one on the haproxy side will quickly be dropped, and once the client decides itself to take a look at the events it received, it will notice that the connection is closed. Regards, Willy
