[TYRUS-250] Sec-WebSocket-Protocol header cannot be present when there is no negotiated subprotocol Created: 13/Sep/13  Updated: 16/Oct/13  Resolved: 13/Sep/13

Status: Resolved
Project: tyrus
Component/s: core
Affects Version/s: 1.3
Fix Version/s: 1.2.2, 1.3

Type: Bug Priority: Major
Reporter: Pavel Bucek Assignee: Pavel Bucek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

RFC6455 section 4.2.2 has the following content:

if the server does not agree to any of the client's requested
subprotocols, the only acceptable value is null. The absence
of such a field is equivalent to the null value (meaning that
if the server does not wish to agree to one of the suggested
subprotocols, it MUST NOT send back a |Sec-WebSocket-Protocol|
header field in its response). The empty string is not the
same as the null value for these purposes and is not a legal
value for this field.



 Comments   
Comment by Pavel Bucek [ 13/Sep/13 ]

fix merged to the master and 1.2.2-SNAPSHOT branches.

corresponding binary bits will be published on java.net maven snapshot repo in 30 mins

Generated at Sun Aug 30 14:52:56 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.