ProxymanApp / ProxymanApp/Proxyman

[Bug] Proxyman breaks web sockets when websocket subprotocols are specified

Open
#1,055 11 comments 1 reaction 1 assignee View on GitHub

@NghiaTranUIT is already working on this.

Since Nov 3, 2021.

✅ Done bug
Dominant language
No language data
Stars
7k
Forks
237
PR merge metrics
No merged PRs in 30d

Description

Proxyman version

23410

macOS Version

11.5.2

Description

We're using a websocket client for graphql subscriptions from a web client.
When Proxyman is started, the web browser is unable to connect to the websocket server.

This is because the graphql subscription library that we use passes a suprotocol at connect time (namely "graphql-ws").
We've been able to isolate the issue in a very simple node server:

proxyman-ws-sample.zip

Steps to reproduce
  • unzip the server
  • npm install
  • node ./server.js

Then

Result
  • if Proxyman is launched, the websocket opened with the "amqp" (*) subprotocol fails, and the websocket with no suprotocol succeeds
  • if Proxyman is not launched, both websockets connect successfully

(*) the subprotocol doesn't impact the result, but at least "amqp" is a well-known subprotocol from IANA registry

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.