[Webkit-unassigned] [Bug 81878] [WebSocket]Reserved1 bit should be 0 when no negotiated extension

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Mar 22 22:01:51 PDT 2012


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





--- Comment #10 from joey <li.yin at intel.com>  2012-03-22 22:01:51 PST ---
(In reply to comment #9)
> (In reply to comment #8)
> >    Do you think it is necessary to design a new test to cover the following case:
> >    It has negotiated extension, but the reserved1 bit is set to be 0.
> 
> Yep, that would be neat.
> This is directly related to this patch, it is all about making sure we correctly check in input of the Reserved bits.

Sorry for my misleading, according to the investigation, this kind of case has been covered by current test, such as zero-length-text.html, receive-blob.html and so on, most of the former test cases based on uncompressed frames. 
So, maybe it's not necessary to design the duplicate case.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list