Short URL: http://html5.org/r/1843
| SVN | Bug | Comment | Time (UTC) |
|---|---|---|---|
| 1843 | Handle TLS errors in the Web Socket Protocol. (and minor editorial fixes) | 2008-07-03 09:05 |
Index: source
===================================================================
--- source (revision 1842)
+++ source (revision 1843)
@@ -39063,7 +39063,7 @@
<p>If the user agent is configured to use a proxy to connect to
port <var title="">port</var>, then connect to that proxy and ask
it to open a TCP/IP connection to the host given by <var
- title="">host</var> to the port given by <var
+ title="">host</var> and the port given by <var
title="">port</var>.</p>
<div class="example">
@@ -39083,7 +39083,7 @@
<p>Otherwise, if the user agent is not configured to use a proxy,
then open a TCP/IP connection to the host given by <var
- title="">host</var> to the port given by <var
+ title="">host</var> and the port given by <var
title="">port</var>.</p>
</li>
@@ -39092,9 +39092,11 @@
Web Socket connection</span> and abort these steps.</p></li>
<li><p>If <var title="">secure</var> is true, perform a TLS
- handshake over the connection. All further communication on this
- channel must run through the encrypted tunnel. <a
- href="#refsRFC2246">[RFC2246]</a></p></li>
+ handshake over the connection. If this fails (e.g. the server's
+ certificate could not be verified), then <span>fail the Web Socket
+ connection</span> and abort these steps. Otherwise, all further
+ communication on this channel must run through the encrypted
+ tunnel. <a href="#refsRFC2246">[RFC2246]</a></p></li>
<li>