[Webkit-unassigned] [Bug 32246] Multiple connection attempts to a WebSocket server should not be allowed

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Apr 15 12:30:33 PDT 2013


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





--- Comment #15 from Joe Mason <jmason at blackberry.com>  2013-04-15 12:28:49 PST ---
(In reply to comment #14)
> (In reply to comment #13)
> > Unsure. I really see this as part of underlying networking code, just like HTTP connection limit enforcement.
> 
> In which file is the HTTP connection limit enforcement implemented? I have found initializeMaximumHTTPConnectionCountPerHost in Source/WebCore/platform/network/ResourceRequestBase.h but it seems not to be used anywhere.

It's not in WebKit - it's part of the underlying platform network stack (the Windows network stack, or the Mac network stack, or libsoup for the GTK+ port, or the Qt network classes for the Qt port, etc.)

I'm not sure websockets are in the same boat as HTTP connection limits. It's assumed that the underlying stack is a complete implementation of the HTTP protocol, but for WebSockets most of the protocol is implemented in WebKit and the "underlying stack" is simply TCP. So any additional limitations that don't apply to TCP connections in general would be more properly be part of the WebSocket protocol code in WebKit than in the network stack.

(To be a completely clean parallel to HTTP, much of the WebSocket code should be removed from webkit and provided through an external library... but that's uselessly pedantic.)

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