-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Impossible to set subprotocol #1
Comments
It's not related to async operation, so you are right. Currently we have no way to fine-tune the response. Unfortunately, If you really want this feature (i.e., setting sub-protocol in the response), I can make a necessary pull-request to vti/protocol-websocket. After the new version of |
Oops. I found OK, I'll try using this to make an interface to customize the request.. |
That would be great! 👍 |
Released version 0.06. |
Thanks a lot, I'll give it a try! |
Perfect, specifying a handshake callback allows me to call subprotocol on the response object! Thanks again. |
I'm glad to hear that. Thanks for reporting. |
I'm rather new to async websocket programming, so I might miss the obvious - but I wasn't able to find a way to set the
Sec-WebSocket-Protocol
of the Response sent byAnyEvent::WebSocket::Server
.The
establish*
methods of the Server implementation useProtocol::WebSocket::Handshake::Server
to create the HTTP 101 response for the received request. However, they do not allow for the application to influence the creation of theProtocol::WebSocket::Response
- so the user cannot set the "subprotocol" field.The text was updated successfully, but these errors were encountered: