| Summary: | ASTERISK-22441: WebSocket response when subprotocol is omitted violates spec | ||
| Reporter: | David M. Lee (dlee) | Labels: | |
| Date Opened: | 2013-09-03 08:46:34 | Date Closed: | 2013-09-13 09:23:04 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_http_websocket |
| Versions: | 12.0.0-alpha1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When I added the possibility of using a default subprotocol on WebSocket connections, the WebSocket server in Asterisk always responds with a {{Sec-WebSocket-Protocol}} indicating the subprotocol actually in use.
[As it turns out|https://github.com/tavendo/AutobahnPython/pull/147#issuecomment-21330341], [the spec|http://tools.ietf.org/html/rfc6455#page-20] actually says the "the client MUST _Fail the WebSocket Connection_" if the client omits the protocol but the server supplies one in its response. Go figure. | ||
| Comments: | |||