[html5] r2978 - [] (0) Limit number of non-established WebSocket connections per client.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-04-24 02:49:45 -0700 (Fri, 24 Apr 2009)
New Revision: 2978

Modified:
   source
Log:
[] (0) Limit number of non-established WebSocket connections per client.

Modified: source
===================================================================
--- source	2009-04-24 07:33:10 UTC (rev 2977)
+++ source	2009-04-24 09:49:45 UTC (rev 2978)
@@ -61919,6 +61919,28 @@
 
    <li>
 
+    <p>If the user agent already has a Web Socket connection to the
+    remote host identified by <var title="">host</var> (even if known
+    by another name), wait until that connection has been <span
+    title="Web Socket connection is established">established</span> or
+    for that connection to have <span title="fail the Web Socket
+    connection">failed</span>.</p>
+
+    <p class="note">This makes it harder for a script to perform a
+    denial of service attack by just opening a large number of Web
+    Socket connections to a remote host.</p>
+
+    <p class="note">There is no limit to the number of <span
+    title="Web Socket connection is established">established</span>
+    Web Socket connections a user agent can have with a single remote
+    host. Servers can refuse to connect users with an excessive number
+    of connections, or disconnect resource-hogging users when
+    suffering high load.</p>
+
+   </li>
+
+   <li>
+
     <p>If the user agent is configured to use a proxy to connect to
     host <var title="">host</var> and/or port <var
     title="">port</var>, then connect to that proxy and ask it to open
@@ -62020,7 +62042,7 @@
 
     <p>If there is no <var title="">protocol</var>, then skip this step.</p>
 
-    <p>Othewrise, send the following bytes:</p>
+    <p>Otherwise, send the following bytes:</p>
 
     <pre>57 65 62 53 6f 63 6b 65  74 2d 50 72 6f 74 6f 63
 6f 6c 3a 20</pre>