In current implement, WebSocket just ignores invalid continuation frames which have no leading frame with FIN=0. cf.) Chromium side issue report: http://code.google.com/p/chromium/issues/detail?id=91193
Created attachment 102641 [details] Patch
Comment on attachment 102641 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=102641&action=review Looks ok. > LayoutTests/ChangeLog:5 > + WebSocket: Should be closed by receiving invalid continuation frame. > + > + https://bugs.webkit.org/show_bug.cgi?id=65527 nit: We don't need a blank line between the summary line and the bug URL. > Source/WebCore/ChangeLog:5 > + WebSocket: Should be closed by receiving invalid continuation frame. > + > + https://bugs.webkit.org/show_bug.cgi?id=65527 ditto.
Comment on attachment 102641 [details] Patch Clearing flags on attachment: 102641 Committed r92260: <http://trac.webkit.org/changeset/92260>
All reviewed patches have been landed. Closing bug.