tyrus
  1. tyrus
  2. TYRUS-250

Sec-WebSocket-Protocol header cannot be present when there is no negotiated subprotocol

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.3
    • Fix Version/s: 1.2.2, 1.3
    • Component/s: core
    • Labels:
      None

      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.

        Activity

        Pavel Bucek created issue -
        Pavel Bucek made changes -
        Field Original Value New Value
        Assignee Pavel Bucek [ pavel_bucek ]
        Pavel Bucek made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Pavel Bucek made changes -
        Fix Version/s 1.2.2 [ 16740 ]

          People

          • Assignee:
            Pavel Bucek
            Reporter:
            Pavel Bucek
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: