Fumitoshi Ukai 4c1c96f7e0 go.net/websocket: fix handshake error. ...

If client sent no subprotocol (e.g. no Sec-WebSocket-Protocol),
websocket server responded with the following header
  HTTP/1.1 101 Switching Protocols
  Upgrade: websocket
  Connection: Upgrade
  Sec-WebSocket-Accept: E7SRWRnZL9RuGFLuZ0j4508nqdg=
  Sec-WebSocket-Protocol:
So, client may close the connection because it contains
wrong empty Sec-WebSocket-Protocol header.

If client didn't offer any subprotocol, don't set
config.Protocol, so that not emit empty Sec-WebSocket-Protocol.

Fixes golang/go#5457.

R=golang-dev, mikioh.mikioh
CC=golang-dev
https://golang.org/cl/9379044

2013-05-14 15:08:31 +09:00

..

client.go

go.net/websocket: allow server configurable

2013-05-12 13:50:10 +09:00

exampledial_test.go

go.net/websocket: fix server and client examples

2012-09-06 15:22:57 +10:00

examplehandler_test.go

go.net/websocket: fix server and client examples

2012-09-06 15:22:57 +10:00

hixie_test.go

go.net: gofix for net/url API changes.

2012-02-18 12:49:41 +11:00

hixie.go

websocket: fix typo

2012-07-30 12:03:42 +10:00

hybi_test.go

go.net/websocket: fix handshake error.

2013-05-14 15:08:31 +09:00

hybi.go

go.net/websocket: fix handshake error.

2013-05-14 15:08:31 +09:00

server.go

go.net/websocket: allow server configurable

2013-05-12 13:50:10 +09:00

websocket_test.go

go.net/websocket: allow server configurable

2013-05-12 13:50:10 +09:00

websocket.go

go.net/websocket: allow server configurable

2013-05-12 13:50:10 +09:00