mirror of https://github.com/gorilla/websocket.git
873e67e4d5
The values of the `Upgrade` and `Connection` response headers can
contain multiple tokens, for example
Connection: upgrade, keep-alive
The WebSocket RFC describes the checking of these as follows:
2. If the response lacks an |Upgrade| header field or the |Upgrade|
header field contains a value that is not an ASCII case-
insensitive match for the value "websocket", the client MUST
_Fail the WebSocket Connection_.
3. If the response lacks a |Connection| header field or the
|Connection| header field doesn't contain a token that is an
ASCII case-insensitive match for the value "Upgrade", the client
MUST _Fail the WebSocket Connection_.
It is careful to note "contains a value", "contains a token".
Previously, the client would reject with "bad handshake" if the header
doesn't contain exactly the value it looks for.
Change the checks to use `tokenListContainsValue` instead, which is
incidentally what the server is already doing for similar checks.
|
||
|---|---|---|
| .circleci | ||
| .github | ||
| examples | ||
| .gitignore | ||
| AUTHORS | ||
| LICENSE | ||
| README.md | ||
| client.go | ||
| client_clone.go | ||
| client_clone_legacy.go | ||
| client_server_test.go | ||
| client_test.go | ||
| compression.go | ||
| compression_test.go | ||
| conn.go | ||
| conn_broadcast_test.go | ||
| conn_test.go | ||
| conn_write.go | ||
| conn_write_legacy.go | ||
| doc.go | ||
| example_test.go | ||
| go.mod | ||
| go.sum | ||
| join.go | ||
| join_test.go | ||
| json.go | ||
| json_test.go | ||
| mask.go | ||
| mask_safe.go | ||
| mask_test.go | ||
| prepared.go | ||
| prepared_test.go | ||
| proxy.go | ||
| server.go | ||
| server_test.go | ||
| trace.go | ||
| trace_17.go | ||
| util.go | ||
| util_test.go | ||
| x_net_proxy.go | ||
README.md
Gorilla WebSocket
Gorilla WebSocket is a Go implementation of the WebSocket protocol.
Documentation
Status
The Gorilla WebSocket package provides a complete and tested implementation of the WebSocket protocol. The package API is stable.
Installation
go get github.com/gorilla/websocket
Protocol Compliance
The Gorilla WebSocket package passes the server tests in the Autobahn Test Suite using the application in the examples/autobahn subdirectory.
Gorilla WebSocket compared with other packages
| github.com/gorilla | golang.org/x/net | |
|---|---|---|
| RFC 6455 Features | ||
| Passes Autobahn Test Suite | Yes | No |
| Receive fragmented message | Yes | No, see note 1 |
| Send close message | Yes | No |
| Send pings and receive pongs | Yes | No |
| Get the type of a received data message | Yes | Yes, see note 2 |
| Other Features | ||
| Compression Extensions | Experimental | No |
| Read message using io.Reader | Yes | No, see note 3 |
| Write message using io.WriteCloser | Yes | No, see note 3 |
Notes:
- Large messages are fragmented in Chrome's new WebSocket implementation.
- The application can get the type of a received data message by implementing a Codec marshal function.
- The go.net io.Reader and io.Writer operate across WebSocket frame boundaries. Read returns when the input buffer is full or a frame boundary is encountered. Each call to Write sends a single frame message. The Gorilla io.Reader and io.WriteCloser operate on a single WebSocket message.