-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
does proxygen have websockets support? #206
Comments
Can you elaborate by what websocket support you would like from proxygen? Proxygen can handle the HTTP interactions required for a websocket handshake (Upgrade headers, send 101 Switching Protocls), but does not provide any native parsing or generating of websocket frames. |
We recently added support for WebSockets. Proxygen handles the handshake part if the application asks for a WebSocket upgrade. To ask for a WebSocket upgrade on a transaction, the HTTPMessage has a call "setEgressWebsocketUpgrade". Responses will similarly be marked with a flag if they contain appropriate WebSocket response headers - this can be checked with a call to "isIngressWebsocketUpgrade" on the HTTPMessage. Note: for now, you would need to add the "Sec-WebSocket-Version" header to the HTTPMessage. This requirement should go away soon. |
Hello does anybody have an example of making a working websocket request? I have been at this for a couple of days and I can't get it to work |
PS: trying various variations of something like this: https://gist.github.com/frenchietechie/47ba9ffa069f359ad99e1dcbf7f7f892 but I keep getting error codes such as Bad RequestYour browser sent a request that this server could not understand. |
Are you connecting to a proxygen server? |
An example has been committed in bc44e34. |
hi ,
does proxygen have websockets support yet?
thanks
The text was updated successfully, but these errors were encountered: