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

Update WebSocket link to RFC6455 #240

Closed
wants to merge 2 commits into from
Closed

Update WebSocket link to RFC6455 #240

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
880feec
Update WebSocket link to RFC6455.
Hywan Apr 24, 2015
fac4dbe
Fix a typo when spelling WebSocket.
Hywan Jul 16, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
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 Web

This comment was marked as off-topic.

Sign in to view

Socket 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