> > As far as i can understand it should not try to send a close message at
> > that point, because the close did already happen from the client side..
> > I guess if onclose was called programatically from the server side then
> it
> > is logical.
> RFC 6455, section 5.5.1
> Close is a two-stage process and closing the TCP connection is the
> server's responsibility.
> Looks like you have a non-spec compliant client.
But that is just a browser that gets an other url loaded (i think kind of
how can that be a 2 way thing?
If i close a tab or i force reload the tab then yes i can get that the
browser can send a close request to the server
But it has to wait for it? I can't believe that many browsers do that?
What if the latency is a few hundred millis?

Johan Compagner

Reply via email to