Skip to content

Commit

Permalink
[e] (0) Define the relationship of WebSocket to HTTP and TCP better.
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.whatwg.org/webapps@3377 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jul 8, 2009
1 parent 1369967 commit 995ceee
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 0 deletions.
1 change: 1 addition & 0 deletions index
Expand Up @@ -71223,6 +71223,7 @@ time:empty { binding: <i title="">time</i>; }</pre>
Alan Plum,
Alastair Campbell,
Alex Nicolaou,
Alex Rousskov,
Alexander J. Vincent,
Alexey Feldgendler,
&#1040;&#1083;&#1077;&#1082;&#1089;&#1077;&#1081; &#1055;&#1088;&#1086;&#1089;&#1082;&#1091;&#1088;&#1103;&#1082;&#1086;&#1074; (Alexey Proskuryakov),
Expand Down
13 changes: 13 additions & 0 deletions source
Expand Up @@ -69295,6 +69295,7 @@ interface <dfn>WebSocket</dfn> {
such a way that its servers can share a port with HTTP servers, by
having its handshake be a valid HTTP Upgrade handshake also.</p>


<h6>Security model</h6>

<p>The Web Socket protocol uses the origin model used by Web
Expand All @@ -69305,6 +69306,17 @@ interface <dfn>WebSocket</dfn> {
arbitrary origin string.</p>


<h6>Relationship to TCP/IP and HTTP</h6>

<p>WebSocket is an independent TCP-based protocol. It's only
relationship to HTTP is that its handshake is interpreted by HTTP
servers as an Upgrade request.</p>

<p>The WebSocket protocol by default uses port 81 for regular
WebSocket connections and port 815 for WebSocket connections
tunneled over TLS.</p>


<!--BOILERPLATE middle-ietf-conformance-->


Expand Down Expand Up @@ -84012,6 +84024,7 @@ time:empty { binding: <i title="">time</i>; }</pre>
Alan Plum,
Alastair Campbell,
Alex Nicolaou,
Alex Rousskov,
Alexander J. Vincent,
Alexey Feldgendler,
&#1040;&#1083;&#1077;&#1082;&#1089;&#1077;&#1081; &#1055;&#1088;&#1086;&#1089;&#1082;&#1091;&#1088;&#1103;&#1082;&#1086;&#1074; (Alexey Proskuryakov),
Expand Down

0 comments on commit 995ceee

Please sign in to comment.