-
Notifications
You must be signed in to change notification settings - Fork 2.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
WebSocket client got closed immidately for some servers #6543
Comments
This was referenced Oct 17, 2023
Ok. The compatible one isn't really compatible. The connection will be closed after 60s. I am sending a message per second so it can't be idle timeout from server side. Logs
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Bun is running?
1.0.6
What platform is your computer?
Darwin 22.4.0 arm64 arm
What steps can reproduce the bug?
bun run this file
https://gist.github.com/xlc/129c41fc4e35246fbc0561d97c9cdccd
What is the expected behavior?
The WebSocket did not get closed and it successfully sent a message and received a response
What do you see instead?
The WebSocket got closed immediately
Additional information
Tried with 3 different servers, two not compatible, and one compatible.
The compatible one is controlled by myself, the other two are not.
Not compatible servers:
Compatible server:
compatible output
The text was updated successfully, but these errors were encountered: