Library does not respect system (or application) proxy settings

Open
#302 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
networking

Research direction

Start by tracing the websocket connection after the API returns its websocket URL, focusing on where proxy settings and credentials could be applied. Reproduce the connection behind the configured NTLM proxy and verify that websocket traffic appears in Fiddler and the connection succeeds.

Written by the indexing model from the issue text.

Description

I'm sitting behind an NTLM-authenticating proxy. In my application, I have in my App.config

  <system.net>
    <defaultProxy enabled="true" useDefaultCredentials="true">
      <proxy usesystemdefault="True"/>
    </defaultProxy>
  </system.net>

The application connects fine and can receive the websocket URL from the API endpoint I'm trying to access, but when websocket-sharp takes over, the connection fails because the library doesn't use the configured proxy.

I have tried to debug the connection in Fiddler but because the library ignores all proxy settings, nothing websocket-related ever shows up there.

Dominant language
C#
Stars
6.1k
Forks
1.7k
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 sta/websocket-sharp

All issues in sta/websocket-sharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.