Client not upgrading to websocket
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Setup: VPN over 3G.
Following behavior identified by Wireshark on server.
Server side is an ASP.Net MVC web application that on GET accepts websocket request and call for switch protocol. Same application behaved correctly in different environments so do not blame it.
Now weird things happen.
Sometimes the client does not upgrade to websocket. Sometimes it does.
I was not able to reproduce this in other network but the one mentioned in setup above.
When the client does not upgrade, sends a FIN/ACK message to server which in response RST the connection.
I went for the SuperWebSocket (WebSocket4Net) client instead, that seems to handle better my setup.
I wrote this in case others came across the same issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named. Start by reproducing the handshake over the stated VPN/3G setup and compare Wireshark traces for successful and failed upgrades; done means a reproducible failure with an agreed expected upgrade outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100