sta / sta/websocket-sharp

unsupported opcodes / IE

Open
#226 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
6.1k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

Hello !

I'm using websocket# to transfer files from ones browser to the server. Those files can be several Go big.

I'm having some troubles with Internet Explorer 11 as sometimes randomly it sends unsupported opcodes like 3,5,7,11,15. This happens mainly on huge files.
I didn't encounter the problem with Firefox nor Chrome so far.

Problem is the websocketServer will throw an exception and close the connection. The browser will throw a close event on the socket and not a error making it hard to identify to make a resume.

Would there be a way to ignore / drop those frames ? I have no idea if that would be critical in the overall process.
Have you ever seen those opcodes ?

Thanks !!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with Internet Explorer 11 while transferring a large file, then inspect the websocket server path that throws on unsupported opcodes. Determine whether those frames can be safely ignored or dropped without corrupting the transfer; the issue provides no named files, tests, or acceptance criteria.

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
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.