Skip to content
This repository was archived by the owner on Nov 6, 2022. It is now read-only.

Commit 4f69be2

Browse files
Hywanindutny
authored andcommitted
readme: update WebSocket link to RFC6455
PR-URL: #240 Reviewed-By: Fedor Indutny <fedor@indutny.com>
1 parent b5bcca8 commit 4f69be2

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ The Special Problem of Upgrade
9494
------------------------------
9595

9696
HTTP supports upgrading the connection to a different protocol. An
97-
increasingly common example of this is the Web Socket protocol which sends
97+
increasingly common example of this is the WebSocket protocol which sends
9898
a request like
9999

100100
GET /demo HTTP/1.1
@@ -106,8 +106,8 @@ a request like
106106

107107
followed by non-HTTP data.
108108

109-
(See http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol-75 for more
110-
information the Web Socket protocol.)
109+
(See [RFC6455](https://tools.ietf.org/html/rfc6455) for more information the
110+
WebSocket protocol.)
111111

112112
To support this, the parser will treat this as a normal HTTP message without a
113113
body, issuing both on_headers_complete and on_message_complete callbacks. However

0 commit comments

Comments
 (0)