Working with Fiddler?
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Has anyone had any luck getting a websocket-sharp connection to be displayed in Fiddler? I've set up Fiddler to listen on port 8888, and I've added this line to my client:
m_webSocket.SetProxy("localhost:8888", "", "");
But I don't see any websocket traffic in Fiddler.
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
Start by reproducing the client connection with Fiddler listening on localhost:8888 and the SetProxy call shown in the issue. Trace the WebSocket client's proxy configuration and compare the observed behavior with Fiddler's expected WebSocket traffic; done means the connection's WebSocket traffic is visible or the compatibility limitation is documented.
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
- 25/100