[Webkit-unassigned] [Bug 173719] New: Response.flush over HTTP/2

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jun 22 09:22:46 PDT 2017


            Bug ID: 173719
           Summary: Response.flush over HTTP/2
           Product: WebKit
           Version: Safari 10
          Hardware: Macintosh
                OS: macOS 10.12.4
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: brett.postin at isams.co.uk


In a version of Safari that supports HTTP/2 (i.e. v9+) running on macOS “El Capitan” v10.11 or newer, when accessing a webpage served from IIS10 via HTTP/2 (e.g. Windows Server 2016 / Windows 10), if the page contains a "Response.Flush" then it will not load. It simply hangs with a white screen. Web server CPU usage also spikes during these occurrences.


The cause of the issue is using Response.Flush. I have only confirmed this in Classic ASP so I do not know about .NET, but removing those lines makes the pages load fine.

This thread (https://forums.iis.net/t/1235574.aspx?Response+Flush+not+working+on+SSL+site+in+classic+ASP) suggests that when Response.Flush is used, IIS switches protocol from HTTP/2 back to HTTP/1.1. Safari cannot handle this, whilst all other browsers seemingly can.

Demos from the link above:

Working - http://limoeventplanner.com/safari-test.asp
Not working - https://limoeventplanner.com/safari-test.asp

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/20170622/ba988df7/attachment.html>

More information about the webkit-unassigned mailing list