fasthttp/websocket issues and pull requests

#40 - build(deps): bump golang.org/x/net from 0.8.0 to 0.17.0

Pull Request - State: closed - Opened by dependabot[bot] 9 months ago - 1 comment
Labels: dependencies

#39 - writing on closed connection without getting error !

Issue - State: open - Opened by mahditakrim about 1 year ago
Labels: question, pending/investigation

#38 - docs: fix comment typos

Pull Request - State: closed - Opened by alexandear about 1 year ago - 1 comment

#37 - refactor: simplify client server tests

Pull Request - State: closed - Opened by alexandear about 1 year ago - 1 comment

#36 - Is there any plan to support websocket client of fasthttp?

Issue - State: closed - Opened by Quons about 1 year ago - 5 comments
Labels: enhancement, help wanted

#35 - Please return different error when server responds with non-101 status code

Issue - State: open - Opened by sirzooro about 1 year ago - 1 comment
Labels: bug

#34 - Migrate from deprecated `io/ioutil`

Pull Request - State: closed - Opened by keystroke3 over 1 year ago - 1 comment

#33 - Migrate from deprected `ioutil` to `io`

Issue - State: closed - Opened by keystroke3 over 1 year ago

#32 - Since gorilla projects are archived, how would it impact this project ?

Issue - State: closed - Opened by kuchaguangjie over 1 year ago - 2 comments

#31 - Description:

Pull Request - State: closed - Opened by gokpm over 1 year ago - 2 comments

#30 - panic nil: websocket.(*Conn).beginMessage

Issue - State: closed - Opened by kuchaguangjie over 1 year ago - 5 comments
Labels: bug

#29 - panic: concurrent write to websocket connection

Issue - State: closed - Opened by kuchaguangjie almost 2 years ago - 5 comments

#28 - Case caused FastHTTPIsWebSocketUpgrade prediction false.

Issue - State: closed - Opened by leopku about 2 years ago

#27 - Bump github.com/valyala/fasthttp from 1.33.0 to 1.34.0

Pull Request - State: closed - Opened by dependabot[bot] over 2 years ago
Labels: dependencies

#26 - Replace flate with the flate pool from fasthttp

Issue - State: closed - Opened by mertakman over 2 years ago - 2 comments
Labels: enhancement

#25 - [BUG] - go get -u error on fetching the project

Issue - State: closed - Opened by sujit-baniya almost 3 years ago - 15 comments

#24 - IsWebsocketUpgrade returning false

Issue - State: closed - Opened by Nv7-GitHub over 3 years ago - 3 comments

#23 - Type mismatch if using Fiber v2

Issue - State: closed - Opened by mattrighetti over 3 years ago - 1 comment

#22 - Beta releases

Issue - State: closed - Opened by mwf over 3 years ago - 3 comments

#21 - added support for websocket client over unix domain sockets

Pull Request - State: closed - Opened by 1800alex over 3 years ago - 1 comment

#20 - Re-uploading v1.4.2 has introduced checksum mismatch

Issue - State: closed - Opened by sylvain-p85 almost 4 years ago - 1 comment

#19 - panic: repeated read on failed websocket connection

Issue - State: closed - Opened by rebootcode about 4 years ago - 1 comment

#18 - Possible to support "nhooyr/websocket" then gorilla/websocket ?

Issue - State: closed - Opened by rebootcode about 4 years ago - 2 comments

#17 - NextWriter() is "slow"

Issue - State: closed - Opened by maxim-ge over 4 years ago - 1 comment

#16 - Upgrade synchronously

Issue - State: closed - Opened by Fenny over 4 years ago - 4 comments

#15 - sec-websocket-protocol values are case insensitive

Issue - State: closed - Opened by observerss over 4 years ago - 1 comment

#14 - Other upgraders?

Issue - State: closed - Opened by betim almost 5 years ago - 3 comments

#13 - sometimes have a panic when client unregistering

Issue - State: closed - Opened by maxjust almost 5 years ago - 13 comments
Labels: bug, pending/investigation

#12 - fix upgrade request header check for most cases

Pull Request - State: closed - Opened by fangli almost 5 years ago - 1 comment

#11 - Incorrect implementation of websocket upgrade header check

Issue - State: closed - Opened by fangli almost 5 years ago - 4 comments

#10 - Project status

Issue - State: closed - Opened by just1689 almost 5 years ago - 1 comment

#9 - I had write a websocket proxy ,but I find in Upgrade method FastHTTPHandler func miss ctx's value

Issue - State: closed - Opened by 59duncom about 5 years ago - 5 comments

#8 - maybe its time to tag new release, use of go mod ...@commithash looks dirty

Issue - State: closed - Opened by maxjust about 5 years ago - 1 comment

#7 - Create SECURITY.md

Pull Request - State: closed - Opened by kirillDanshin about 5 years ago

#6 - panic in WriteMessage

Issue - State: closed - Opened by MasterDimmy over 5 years ago - 4 comments

#5 - how do i detect a client disconnection?

Issue - State: closed - Opened by hiqbn over 5 years ago - 1 comment

#4 - fasthttp/websocket doesnt work with nats.io

Issue - State: closed - Opened by hiqbn over 5 years ago - 14 comments

#3 - Add context-aware upgrader

Pull Request - State: closed - Opened by romshark over 5 years ago - 3 comments

#2 - Fix and improve the README

Pull Request - State: closed - Opened by romshark over 5 years ago

#1 - Can you remake this a clone of gorilla/websocket library?

Issue - State: closed - Opened by tamalsaha almost 6 years ago - 2 comments
Labels: question

GitHub / fasthttp/websocket issues and pull requests