Serveur type

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp, flask
Domain
networking

Research direction

No source files or tests are named. Start by reproducing the WebSocket connection against the reported Flask server and compare its handshake with the working localhost and demo endpoints, focusing on the unsupported-header error. Done means the compatibility cause is identified and a connection to the Flask server works or the unsupported server behavior is clearly documented.

Written by the indexing model from the issue text.

Description

Hello, I wanted to know if it works for any type of server, such as servers created with flask?
Because on some test servers I can connect, but on mine, I can't. "Error! The WebSocket request or response contained unsupported header(s)".
While on ws://localhost:8080 or wss://demo.websocket.me/v3/channel_1?api_key=oCdCcMPQpbvNjUIzqtvF1d2X2okWpDQj4AwARJuAgtjhzKxVEjQU6IdCjwm&notify_self
I can connect.

If you have an idea you save my life!

Dominant language
C#
Stars
1.7k
Forks
206
No merged PRs in 30d

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.

More from endel/NativeWebSocket

All issues in endel/NativeWebSocket

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.