[Webkit-unassigned] [Bug 185924] New: Using fetch(...).then(res => res.body.getReader()) behaves incorrectly over a TLS connection sometimes.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed May 23 16:05:59 PDT 2018


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

            Bug ID: 185924
           Summary: Using fetch(...).then(res => res.body.getReader())
                    behaves incorrectly over a TLS connection sometimes.
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: dingoeatingfuzz at gmail.com

Specific Webkit version: WebKit 13606.1.17.2.2

Using fetch(...).then(res => res.body.getReader()) behaves incorrectly over a TLS connection sometimes.

The exact behavior is the following:

1. Request is made
2. Connection is established, promise is resolved
3. No errors are thrown, but chunks aren't read via reader.read()

The expected behavior:

1. Request is made
2. Connection is established, promise is reoslved
3. Chunks are read via reader.read() until the connection is closed

I have four URLs to share. The first two show streaming working over http and not working over https:

1. Working over HTTP: http://nomad-demo-1872017027.us-east-1.elb.amazonaws.com/ui/allocations/ec21f87c-2866-e0c8-d449-c947fd2c3883/mongo/logs
2. Not working over HTTPS: https://demo.nomadproject.io/ui/allocations/ec21f87c-2866-e0c8-d449-c947fd2c3883/mongo/logs

The third and fourth are an attempt at a minimal reproduction, except streaming works over https in this case:

3. Working over HTTP: http://safari-streaming.mlange.io
4. Working over HTTPS: https://safari-streaming.mlange.io

I suspect this has to do with either the chunk size or perhaps the TLS cipher? I dunno, I'm hoping to learn more!

-- 
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/20180523/05474ca4/attachment.html>


More information about the webkit-unassigned mailing list