[Webkit-unassigned] [Bug 202401] New: Safari 13 truncates websocket payload when x-webkit-deflate-frame is used

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Oct 1 06:03:40 PDT 2019


            Bug ID: 202401
           Summary: Safari 13 truncates websocket payload when
                    x-webkit-deflate-frame is used
           Product: WebKit
           Version: Other
          Hardware: Macintosh
                OS: macOS 10.14
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: volodymyr.sorokin at grammarly.com

Since Safari 13.0 release, webkit starts to truncate websocket's payload to 4092 bytes when 'x-webkit-deflate-frame' extension is used.

The issue is fairly easy to reproduce - just send to a websocket any data whose compressed size is 5kb or more.

Moreover, the websocket (most likely the deflator component) on the browser side also gets 'corrupted' once a large message is sent. This leads to a 'Failed to compress frame' error in console on subsequent attempts to send more messages (even small messages) to the socket.

This behavior is only reproducible when 'x-webkit-deflate-frame' extension enabled. 
If server rejects the extension - then browser behaves correctly and the payload does not get truncated, but obviously the compression is not used in this case.

Safari 12 does not have this issue. In Safari 12 the 'x-webkit-deflate-frame' extension behaves as expected and large payload does not get truncated.

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/20191001/d0781512/attachment-0001.html>

More information about the webkit-unassigned mailing list