Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / kerryjiang/websocket4net issues and pull requests
#206 - SocketException: The requested name is valid, but no data of the requested type was found
Issue -
State: open - Opened by brako 28 days ago
#205 - fire DataReceived
Issue -
State: open - Opened by apobekiaris about 2 months ago
#204 - Unhandled Exception in WebSocket4Net.WebSocket.OnConnected() at 0.15.2
Issue -
State: open - Opened by jercymat 3 months ago
#203 - Your demo code does not work at all? How to make this package work?
Issue -
State: closed - Opened by jonmdev 4 months ago
- 7 comments
#202 - MASK might not be set properly
Issue -
State: closed - Opened by realcoloride 6 months ago
- 3 comments
#201 - Revert "Add support for custom headers"
Pull Request -
State: closed - Opened by realcoloride 6 months ago
- 1 comment
#200 - Add support for custom headers
Pull Request -
State: closed - Opened by realcoloride 6 months ago
- 3 comments
#199 - WebSocket4Net for modern .NET (.NET core) is ready for test
Issue -
State: open - Opened by kerryjiang 8 months ago
- 5 comments
#198 - #197 mirror package readme
Pull Request -
State: closed - Opened by thompson-tomo 10 months ago
#197 - Mirror repo readme as package readme
Issue -
State: closed - Opened by thompson-tomo 10 months ago
#196 - #195 add repo url
Pull Request -
State: closed - Opened by thompson-tomo 10 months ago
#195 - Set Licence type & repo url on package info
Issue -
State: closed - Opened by thompson-tomo 11 months ago
#194 - Security vulnerability requires upgrading System.Net.Security to 4.3.2 or later
Issue -
State: closed - Opened by murjev almost 3 years ago
- 6 comments
Labels: wontfix
#193 - Unable to connect in .NET Framework v4.8
Issue -
State: closed - Opened by AntiTenzor about 3 years ago
- 2 comments
Labels: wontfix
#192 - nuget 上的 WebSocket4Net 0.15.2 看起来不是 master 版本 ?
Issue -
State: closed - Opened by kklldog about 3 years ago
- 2 comments
#191 - Ticket-Based authentication
Issue -
State: closed - Opened by ronaldowww over 3 years ago
- 1 comment
#190 - Exception on WebSocket.FinishCloseTask ()
Issue -
State: closed - Opened by AndreasReitberger over 3 years ago
- 1 comment
#189 - Websocket is closed immediately after opening on Android
Issue -
State: closed - Opened by tungntEmotiv over 3 years ago
- 1 comment
#188 - Is this supported in Android?
Issue -
State: closed - Opened by sandeepsmartest over 3 years ago
- 1 comment
#187 - WSS无法连接
Issue -
State: closed - Opened by qinxg over 3 years ago
- 2 comments
#186 - Multiple subprotocol not able to set & after connection is successful not able to get selected subprotocol
Issue -
State: open - Opened by osakishore over 3 years ago
Labels: question
#185 - WebSocket.NoSilverlight.cs v0.15 forces usage of insecure SslProtocols.Default
Issue -
State: closed - Opened by maxmeffert over 3 years ago
- 1 comment
#184 - How can i use library in C # asp.net MVC?
Issue -
State: closed - Opened by RssFra97 over 3 years ago
- 1 comment
#183 - How to connect using STOMP protocol?
Issue -
State: closed - Opened by sFireFrog almost 4 years ago
- 1 comment
#182 - 默认TLS1.0,可以改成TLS1.2
Issue -
State: closed - Opened by sln162 about 4 years ago
- 5 comments
#181 - Why does my socket always close after "41"?
Issue -
State: closed - Opened by 1337vida about 4 years ago
- 2 comments
#180 - License type
Issue -
State: closed - Opened by itsho about 4 years ago
- 2 comments
#179 - main branch, in WebSocket.OpenAsync() method
Issue -
State: closed - Opened by jason-shi about 4 years ago
- 3 comments
Labels: bug
#178 - Can't connect with wss
Issue -
State: closed - Opened by Hanshan8023 about 4 years ago
- 2 comments
#177 - wss issue "The client and server cannot communicate, because they do not possess a common algorithm"
Issue -
State: closed - Opened by Sergio1C over 4 years ago
- 2 comments
#176 - "It" is websocket implementation - great, but how to start?
Issue -
State: closed - Opened by dylanh724 over 4 years ago
- 1 comment
#175 - Websocket client refuses to connect to a Glitch project websocket server
Issue -
State: closed - Opened by Andrew-Eathan over 4 years ago
- 1 comment
#174 - 中文出现乱码
Issue -
State: closed - Opened by hsxyhao over 4 years ago
- 6 comments
#173 - I get an exception. System.ArgumentException: An item with the same key has already been added. Key: Date
Issue -
State: open - Opened by MakcStudio over 4 years ago
- 1 comment
#172 - Not work with domain
Issue -
State: closed - Opened by ghost over 4 years ago
- 1 comment
#171 - Cannot Open Connection to wss://echo.wss-websocket.net, getting error "Authentication failed because the remote party has closed the transport stream."
Issue -
State: open - Opened by ronaldowww almost 5 years ago
#170 - Cannot send data unless an event is currently active
Issue -
State: open - Opened by NateKomodo almost 5 years ago
- 6 comments
#169 - The process was terminated due to an unhandled exception.
Issue -
State: closed - Opened by allmyfantasy almost 5 years ago
- 1 comment
#168 - UWP app with TLS 1.2 not working
Issue -
State: open - Opened by vishy007 almost 5 years ago
- 1 comment
#167 - TLS 1.2 support in Win 8.1 and Win 7
Issue -
State: closed - Opened by vishy007 almost 5 years ago
- 2 comments
#166 - Stopping the Server process does not send a close status code.
Issue -
State: open - Opened by matthewsanders about 5 years ago
- 1 comment
Labels: bug
#165 - EXCEPTION Exception !!!: System.NullReferenceException at WebSocket4Net.Protocol.DraftHybi10Processor.SendHandshake
Issue -
State: closed - Opened by srborha about 5 years ago
- 4 comments
#164 - clientstate always open after server closed
Issue -
State: closed - Opened by shijinglin about 5 years ago
- 1 comment
#163 - System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
Issue -
State: open - Opened by prajilal over 5 years ago
- 4 comments
#162 - Make sure WebSocket fired all Closed events when Disposing
Issue -
State: open - Opened by darxis over 5 years ago
Labels: bug
#161 - パッケージを再構築
Pull Request -
State: closed - Opened by kenjiuno over 5 years ago
- 1 comment
#160 - System.Exception: HTTP/1.1 200 OK
Issue -
State: closed - Opened by Rombersoft over 5 years ago
- 2 comments
#159 - Why is WebSocket4Net client closing socket with 1011 error?
Issue -
State: closed - Opened by CaledoniaProject over 5 years ago
- 2 comments
#158 - HTTP/1.1 431 Request Header Fields Too Large
Issue -
State: open - Opened by BZ-CO over 5 years ago
- 1 comment
#157 - wss HTTP/1.1 101
Issue -
State: open - Opened by cfz1025 over 5 years ago
- 2 comments
#156 - DraftHybi10Processor.SendHandshake NullReferenceException
Issue -
State: open - Opened by MiloszPawlowski over 5 years ago
#155 - websocket4Net client connect BET365,some returned data is gibberish
Issue -
State: open - Opened by lijing2001 over 5 years ago
- 1 comment
#154 - Packet loss points at resources not being disposed correctly internally
Issue -
State: open - Opened by shinkathe over 5 years ago
#153 - Support system proxy by default
Issue -
State: open - Opened by jamesmcguirepro over 5 years ago
#152 - 无法连接
Issue -
State: closed - Opened by hjj28810 over 5 years ago
- 1 comment
#151 - Method Not found issue?
Issue -
State: open - Opened by LiHanQing over 5 years ago
#150 - 难得国人分享,有生产环境使用案例吗?
Issue -
State: closed - Opened by taomylife521 almost 6 years ago
- 1 comment
#149 - An existing connection was forcibly closed by the remote host.
Issue -
State: open - Opened by cmoles almost 6 years ago
- 1 comment
#148 - Issue with simple wss
Issue -
State: open - Opened by ahvahsky2008 almost 6 years ago
- 1 comment
#147 - How To Read Data Received?
Issue -
State: closed - Opened by MrDevDevy about 6 years ago
#146 - Lack of proxy support with credentials
Issue -
State: open - Opened by mamchech about 6 years ago
- 2 comments
#145 - Unhandled NullReferenceException in Sending_Completed
Issue -
State: open - Opened by pvginkel about 6 years ago
#144 - The webSocket connection is successful and then disconnected
Issue -
State: open - Opened by LiangWeixin about 6 years ago
#143 - Unhandled NullReferenceException (FireMessageReceived)
Issue -
State: open - Opened by 80dB about 6 years ago
#142 - JsonWebSocket How to deal with the received information?
Issue -
State: open - Opened by liangruiben about 6 years ago
#141 - Unhandled "cannot access a disposed object" exception
Issue -
State: open - Opened by LolliDepp over 6 years ago
- 6 comments
#140 - websocket4net with ssl certificate
Issue -
State: open - Opened by PremjithS over 6 years ago
#139 - Socket not properly clean up, if connection drop
Issue -
State: open - Opened by humblecscoder over 6 years ago
- 1 comment
#138 - Closed behaviour change after 0.14.1
Issue -
State: open - Opened by ghost over 6 years ago
#137 - Looking for commit id of NuGet package release
Issue -
State: closed - Opened by dxdxdt over 6 years ago
- 2 comments
#136 - superwebsocket url中的path长度超过508个字符时无法连接
Issue -
State: closed - Opened by Imagine-Brian over 6 years ago
- 1 comment
#135 - Unzipping incoming traffic
Issue -
State: open - Opened by siberianguy over 6 years ago
#134 - Charset issue
Issue -
State: open - Opened by ahvahsky2008 almost 7 years ago
#133 - [Feature] Add websocket interface
Pull Request -
State: closed - Opened by dougdellolio almost 7 years ago
- 2 comments
#132 - Exclude origin from header
Issue -
State: open - Opened by juppjupp almost 7 years ago
- 2 comments
#131 - .NET Standard 2.0
Issue -
State: open - Opened by breyed almost 7 years ago
- 11 comments
#130 - Interface for WebSocket class?
Issue -
State: open - Opened by rktect almost 7 years ago
#129 - Async Support?
Issue -
State: closed - Opened by imaji almost 7 years ago
#128 - PusherClient has CTOR not found error with latest version of WebSocket4Net
Issue -
State: open - Opened by galgitron almost 7 years ago
- 18 comments
#127 - WebSocket.Open() doesn't hold application open.
Issue -
State: open - Opened by IKnowBashFu almost 7 years ago
#126 - Subprotocol mismatch should not happen if response protocol doesn't exist
Issue -
State: open - Opened by skyline75489 almost 7 years ago
#125 - Sending big messages failing
Issue -
State: closed - Opened by bPoller2810 almost 7 years ago
- 1 comment
#124 - Exception throw within OnError did not stop
Issue -
State: open - Opened by raytangRT almost 7 years ago
#123 - Refactor with CodeMaid
Pull Request -
State: open - Opened by z3nth10n about 7 years ago
#122 - Update WebSocket4Net.nuspec
Pull Request -
State: open - Opened by moshegutman about 7 years ago
#121 - Unhandled NullReferenceException
Issue -
State: open - Opened by 80dB about 7 years ago
- 2 comments
#120 - Multiplex Web Socket support
Issue -
State: open - Opened by siberianguy about 7 years ago
- 1 comment
#119 - Memory leak on sending byte array
Issue -
State: open - Opened by Grimones about 7 years ago
#113 - NullReferenceException at WebSocket4Net.Protocol.DraftHybi10Processor.SendMessage
Issue -
State: closed - Opened by drweeto over 7 years ago
- 6 comments
Labels: bug
#108 - Xamarin.Android throws not implemented exception
Issue -
State: open - Opened by rusty21 over 7 years ago
- 28 comments
Labels: bug
#104 - Websocket4net doesn't terminate connection
Issue -
State: open - Opened by Radzhab over 7 years ago
- 9 comments
#103 - permessage-deflate
Issue -
State: open - Opened by schulz3000 over 7 years ago
- 1 comment
#100 - When trying to re-open a closed websocket I am getting SocketException "Operation not supported"
Issue -
State: open - Opened by graboszczak over 7 years ago
- 2 comments
#99 - Re-open a closed websocket, get an exception of "An unhandled exception of type
Issue -
State: open - Opened by jliu1970 over 7 years ago
- 4 comments
#98 - IndexOutOfRangeException in WebSocket4Net.Protocol.WebSocketDataFrame.get_FIN()
Issue -
State: open - Opened by jbrestan over 7 years ago
#97 - NullReferenceExceptionObject in `SuperSocket.ClientEngine.ConnectAsyncExtension.SocketConnectCompleted`
Issue -
State: closed - Opened by marto83 over 7 years ago
- 3 comments
#96 - Getting 401 when connecting
Issue -
State: closed - Opened by BIERAAP over 7 years ago
- 3 comments
#95 - dotnet core supported or not?
Issue -
State: closed - Opened by TroelsL over 7 years ago
- 2 comments
#94 - TLS based two way authentication
Issue -
State: closed - Opened by jliu1970 over 7 years ago
- 22 comments
#93 - Update ProtocolProcessorBase.cs
Pull Request -
State: closed - Opened by bwhiton over 7 years ago
- 1 comment