[Webkit-unassigned] [Bug 89002] [Qt] Enable HTTP pipelining

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jun 13 14:33:05 PDT 2012


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


Keith Kyzivat <keith.kyzivat at nokia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |keith.kyzivat at nokia.com




--- Comment #1 from Keith Kyzivat <keith.kyzivat at nokia.com>  2012-06-13 14:33:05 PST ---
There is good reason not to just turn on HTTP Pipelining by default.  This has been discussed in the past - see bug 64169.

There can be long-lived connections that can hold-up other connections.
For example http long polling, where a connection to a server remains open, without any response being sent by the server until there is an event to deliver, allowing for server->client asynchronous communication [1].  HTTP 1.1 mandates that responses need to be done in the same order as the requests[2], thus the requests that come after the http long polling connection are held up until the server decides to respond, which could be as long as 300 seconds[3], but probably more likely to be somewhere between 30 and 120 seconds to avoid timeouts by proxies.  

Now, servers that do HTTP long-polling are stretching the definition of HTTP, and are definitely not following the spirit of the standard, so we could take the stance that we don't care about that kind of content, and allow it to be broken, but it will make other sites suffer.

Markus Goetz mentions in https://bugs.webkit.org/show_bug.cgi?id=64169#c8 that this could be enabled if we can turn it off for requests emanating from javascript...

1 - http://tools.ietf.org/html/draft-loreto-http-bidirectional-07 synpsis
2 - http://en.wikipedia.org/wiki/HTTP_pipelining
3 - http://tools.ietf.org/html/draft-loreto-http-bidirectional-07#section-5.5

-- 
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