- From: poot <cvsmail@w3.org>
- Date: Thu, 3 Jul 2008 18:09:31 +0900 (JST)
- To: public-html-diffs@w3.org
Handle TLS errors in the Web Socket Protocol. (and minor editorial fixes) (whatwg r1843) (changed by: Ian Hickson) Diffs for this change per section: http://people.w3.org/mike/diffs/html5/spec/Overview.1.1032.html#ws-ua-1 Current content per affected section: http://dev.w3.org/html5/spec/Overview.html#ws-ua-1 Previously published WD content per affected section: http://www.w3.org/TR/2008/WD-html5-20080610/single-page/#ws-ua-1 Cumulative diff: http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1031&r2=1.1032&f=h http://html5.org/tools/web-apps-tracker?from=1842&to=1843 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.1031 retrieving revision 1.1032 diff -u -d -r1.1031 -r1.1032 --- Overview.html 3 Jul 2008 09:03:51 -0000 1.1031 +++ Overview.html 3 Jul 2008 09:06:00 -0000 1.1032 @@ -41611,7 +41611,7 @@ <li> <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 + TCP/IP connection to the host given by <var title="">host</var> and the port given by <var title="">port</var>.</p> <div class=example> @@ -41629,7 +41629,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="">port</var>.</p> + and the port given by <var title="">port</var>.</p> <li> <p>If the connection could not be opened, then <a href="#fail-the">fail @@ -41637,8 +41637,11 @@ <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="#references">[RFC2246]</a> + the connection. If this fails (e.g. the server's certificate could not + be verified), then <a href="#fail-the">fail the Web Socket + connection</a> and abort these steps. Otherwise, all further + communication on this channel must run through the encrypted tunnel. <a + href="#references">[RFC2246]</a> <li> <p>Send the following bytes to the remote side (the server):</p>
Received on Thursday, 3 July 2008 09:10:09 UTC