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

Commit

Permalink
readme: update WebSocket link to RFC6455
Browse files Browse the repository at this point in the history
PR-URL: #240
Reviewed-By: Fedor Indutny <fedor@indutny.com>
  • Loading branch information
Hywan authored and indutny committed Jul 19, 2015
1 parent b5bcca8 commit 4f69be2
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ The Special Problem of Upgrade
------------------------------

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

GET /demo HTTP/1.1
Expand All @@ -106,8 +106,8 @@ a request like

followed by non-HTTP data.

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

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

0 comments on commit 4f69be2

Please sign in to comment.