Skip to content

Sec-WebSocket-Protocol header not supported #608

Closed

Description

@nik17klika

Expected Behavior

When client sends handshake it should be able to set "Sec-WebSocket-Protocol" header to establish connection, also Server should send "Sec-WebSocket-Protocol" header in handshake response

Current Behavior

No "Sec-WebSocket-Protocol" supported

Possible Solution

Update Draft_6455 class at least to return "Sec-WebSocket-Protocol" in server response, and think how customize client request post processing to set "Sec-WebSocket-Protocol" header value.

Activity

  1. marci4 commented on Nov 15, 2017

    @marci4
    Collaborator

    Hello @nik17klika,

    thank you for your feature request.

    I will try to set something up tonight!
    Can I then get some feedback from you?

    Greetings
    marci4

  2. added a commit that references this issue on Nov 15, 2017
  3. marci4 commented on Nov 15, 2017

    @marci4
    Collaborator

    Hello @nik17klika,

    I implemented some changes on this branch.
    Could you please take a look at this and tell me if this is sufficient. Thank you!

    To apply a protocol, you have to use call the constructor of the Draft_6455 the following way!
    new Draft_6455( Collections.<IExtension>emptyList(), Collections.<IProtocol>singletonList( new Protocol( "chat" )))
    This adds the Sec-WebSocket-Protocol "chat" to the handshake and the connection!

    Greetings
    marci4

  4. self-assigned this
    on Nov 15, 2017
  5. nik17klika commented on Nov 16, 2017

    @nik17klika
    Author

    Hello @marci4 ,
    thanks for fast response, I guess your changes enough to use Sec-WebSocket-Protocol header

  6. added this to the Release 1.3.7 milestone on Nov 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions