-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Issues: gorilla/websocket
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
After connecting to websocket, the server prints the following log each time it receives a message: read/write on closed pipe.
bug
#919
opened May 23, 2024 by
keaipeng123
1 task done
[BUG] <title>panic: concurrent write to websocket connection
bug
#918
opened May 20, 2024 by
fanziyan
1 task done
[BUG] panic: concurrent write to websocket connection
bug
#913
opened Apr 29, 2024 by
gzw13999
1 task done
Why does specifying the proxy address not work?
bug
#892
opened Jan 24, 2024 by
stricklandye
1 task done
[FEATURE] Provide an override for
isValidChallengeKey
using a custom validator
#882
opened Dec 11, 2023 by
jonbarrow
1 task done
[BUG] 1.5.1: use of closed network connection, 1.5.0 is fine
bug
#877
opened Nov 28, 2023 by
bmhatfield
1 task done
[Question] <traffic from local machine to websocket server is high>
bug
#876
opened Nov 28, 2023 by
zhouziyan
1 task done
[BUG] Dialer type registered unconditionally into proxy
bug
#867
opened Nov 15, 2023 by
imirkin
1 task done
[BUG] Getting "websocket: internal error, unexpected bytes at end of flate stream" despite protecting write calls with mutex
bug
#858
opened Oct 20, 2023 by
NeonWizard
1 task done
[question] concurrent write to websocket connection with mutex.Lock()
question
#828
opened Nov 18, 2022 by
Jrenk
[bug] Can't establish websocket connection when using
NetDialTLSContext
and Proxy
together
bug
#779
opened May 4, 2022 by
sleeyax
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.