| Ticket UUID: | bb5f70d7ddc9d07ae9000af2715f430b559c558c | |||
| Title: | Client's sub-protocol preference not respected | |||
| Type: | Bug | Version: | 1.3 | |
| Submitter: | anonymous | Created on: | 2014-08-11 08:35:04 | |
| Subsystem: | websocket | Assigned To: | emmanuel | |
| Priority: | 5 Medium | Severity: | Important | |
| Status: | Open | Last Modified: | 2014-08-12 13:30:09 | |
| Resolution: | None | Closed By: | nobody | |
| Closed on: | ||||
| Description: |
RFC 6455 indicates that sub-protocols specified by clients (Sec-Websocket-Protocol) come ordered by preference. The WebSocket library currently does not respect the client's preference, nor allows servers to specify which subprotocol to choose when multiple can satisfy the request. In my opinion, the WebSocket library should default to respecting the client preference, and should allow servers to override that preference by specifying priorities for different handlers. [1]: http://tools.ietf.org/html/rfc6455#section-4.1, client handshake requirements, item 10. | |||
| User Comments: |
emmanuel added on 2014-08-12 13:30:09:
You are right, I had not overseen this in the specification and never have had to use it. There is an embryo to an implementation in websocket::test, what would you propose as an API for this? | |||
Home
Blog
Docs
Downloads
Tickets
Timeline
Branches
Tags
Wiki