[AWS] Google Chrome + AWS WebSockets + refresh = sockets stuck in CLOSE_WAIT forever

[Pascal Obry]

Thomas,

> Of special interest is that everytime you refresh the page when using
> Firefox the demo emits one of these messages:
> 
> Received : Connection_Close GOING_AWAY,
> 
> It's apparent that Firefox plays nice with the AWS WebSocket
> implementation, and just as clear that Chrome is not playing nice. Who's
> to blame is unknown to me, but as it stands using AWS WebSockets with
> Google Chrome appears to be a rather dangerous project, as you will
> flood your system with "dead" sockets.

Frankly my experience with WebSocket is still young but to me Firefox is
the one which is correct. It is mandatory for the client to send a
close-connection message to the server. If this is not done the server
cannot tell if the client is still there. When reloading a page a close
connection must be sent as the previous page is not existing anymore...

Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|    http://www.obry.net  -  http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B