[e] (0) Remove completely bogus example.

git-svn-id: http://svn.whatwg.org/webapps@4398 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Dec 3, 2009 · b22fa61 · b22fa61
1 parent d0cc735
commit b22fa61
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 42 deletions.
diff --git a/complete.html b/complete.html
@@ -67144,26 +67144,6 @@ <h6 id=websocket-location><span class=secno>10.3.4.7.6 </span><dfn title=http-we
   server, port, and path, instead of relying on the server to verify
   that the requested host, port, and path are correct.</p>
 
-  <div class=example>
-
-   <p>For example, consider a server running on port 20000 of a shared
-   virtual host, on behalf of the author of www.example.com, which is
-   hosted on that server. The author of the site hostile.example.net,
-   also hosted on the same server, could write a script to connect to
-   port 20000 on hostile.example.net; if neither the client nor the
-   server verified that all was well, this would connect, and the
-   author of the site hostile.example.net could then use the resources
-   of www.example.com.</p>
-
-   <p>With the Web Socket protocol, though, the server responds with a
-   <code>WebSocket-Location</code> header in the handshake, explicitly
-   saying that it is serving <code title="">ws://www.example.com:20000/</code>. The client, expecting
-   (in the case of its use by the hostile author) that the
-   <code>WebSocket-Location</code> be <code title="">ws://hostile.example.net:20000/</code>, would abort the
-   connection.</p>
-
-  </div>
-
 
 
 
@@ -86747,6 +86727,7 @@ <h3 class="no-num">Reflecting IDL attributes</h3>
   Tommy Thorsen,
   Travis Leithead,
   Tyler Close,
+  Vladimir Katardjiev,
   Vladimir Vuki&#263;evi&#263;,
   voracity,
   Wakaba,

diff --git a/index b/index
@@ -78591,6 +78591,7 @@ interface <a href=#htmldocument>HTMLDocument</a> {
   Tommy Thorsen,
   Travis Leithead,
   Tyler Close,
+  Vladimir Katardjiev,
   Vladimir Vuki&#263;evi&#263;,
   voracity,
   Wakaba,

diff --git a/source b/source
@@ -76612,28 +76612,6 @@ multi-origin semantics described in [ORIGIN] applying. (http-origin)
   server, port, and path, instead of relying on the server to verify
   that the requested host, port, and path are correct.</p>
 
-  <div class="example">
-
-   <p>For example, consider a server running on port 20000 of a shared
-   virtual host, on behalf of the author of www.example.com, which is
-   hosted on that server. The author of the site hostile.example.net,
-   also hosted on the same server, could write a script to connect to
-   port 20000 on hostile.example.net; if neither the client nor the
-   server verified that all was well, this would connect, and the
-   author of the site hostile.example.net could then use the resources
-   of www.example.com.</p>
-
-   <p>With the Web Socket protocol, though, the server responds with a
-   <code>WebSocket-Location</code> header in the handshake, explicitly
-   saying that it is serving <code
-   title="">ws://www.example.com:20000/</code>. The client, expecting
-   (in the case of its use by the hostile author) that the
-   <code>WebSocket-Location</code> be <code
-   title="">ws://hostile.example.net:20000/</code>, would abort the
-   connection.</p>
-
-  </div>
-
 
 
 
@@ -97012,6 +96990,7 @@ interface <span>HTMLDocument</span> {
   Tommy Thorsen,
   Travis Leithead,
   Tyler Close,
+  Vladimir Katardjiev,
   Vladimir Vuki&#x0107;evi&#x0107;,
   voracity,
   Wakaba,