[Webkit-unassigned] [Bug 278313] WebSocket close event is not fired when close() is called.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=278313

Andrew Hodel <andrewhodel at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|MOVED                       |---

--- Comment #10 from Andrew Hodel <andrewhodel at gmail.com> ---
You can cause other browsers to do this by dropping the traffic at the server with iptables.

However, with most browsers other than the iPad removing the drop rule invokes the close event as a packet with a FIN flag is sent from the server if the server already closed the tcp socket by it's timeout and the browser's machine tries to reuse it.

The iPad sits and waits until it has a timeout, and the WebSocket constructor does not allow you to set a timeout.

This is important information.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240828/ebeb969d/attachment.htm>