-
-
Notifications
You must be signed in to change notification settings - Fork 80
Issues: vapor/websocket-kit
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
How can I use this library to access it via socks5 proxy?
enhancement
New feature or request
#153
opened Jul 17, 2024 by
ljh740
Add "isConnected" or something to New feature or request
WebSocketClient
class
enhancement
#152
opened Jun 21, 2024 by
edonv
Add access to Request or headers in New feature or request
onUpgrade
closure on client-side
enhancement
#151
opened Jun 20, 2024 by
edonv
NIOCore/NIOLoopBound.swift:120: Precondition failed in 2.14.0
bug
Something isn't working
#140
opened Jun 14, 2023 by
jhoughjr
Massive 100% CPU load when receiving multi frame WebSocket message
bug
Something isn't working
#97
opened Jul 22, 2021 by
hishnash
TLS test with a websocket-kit server and client
enhancement
New feature or request
#92
opened May 19, 2021 by
EthanLozano
Should be able to force close the WebSocket
enhancement
New feature or request
#90
opened May 18, 2021 by
lmcd
connect does not notify the user when a websocket connection isn't upgraded
bug
Something isn't working
#82
opened Nov 28, 2020 by
EthanLozano
WebSocket doesn't respect ServerQuiescingHelper
enhancement
New feature or request
#78
opened Aug 14, 2020 by
tanner0101
ProTip!
Mix and match filters to narrow down what youβre looking for.