starred/Proxyman
1
0
Fork 0
mirror of https://github.com/ProxymanApp/Proxyman.git synced 2026-04-26 08:35:53 +03:00
Code Issues 1.2k Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #815] WebSocket connection requests are held up by Proxyman until the client sends the first message #810

New issue
Closed
opened 2026-03-03 19:22:06 +03:00 by kerem · 7 comments
kerem commented 2026-03-03 19:22:06 +03:00
Owner
Copy link

Originally created by @DL444 on GitHub (Mar 12, 2021).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/815

Originally assigned to: @NghiaTranUIT on GitHub.

Proxyman version? (Ex. Proxyman 1.4.3)

2.19.0

macOS Version? (Ex. mac 10.14)

11.2.3

Steps to reproduce

  1. First test without Proxyman running.
  2. Visit https://www.piesocket.com/websocket-tester
  3. Click Connect.
  4. Note that immediately after connecting you will receive an initial message that looks like {"info":"You are using a test api key"}. This means the server has received your connection request.
  5. Disconnect from server.
  6. Setup Proxyman proxy and enable TLS decryption for demo.websocket.me
  7. Click Connect again.
  8. The WebSocket request shows up in Proxyman with a yellow indicator. Note that the initial message previously received is not shown.
  9. Wait for a moment to confirm that the request stays in this state indefinitely.
  10. Click Send to send a message.
  11. The request indicator in Proxyman turns green, the initial message appears, and the server echos your message. This proves that the server will not receive connection request before the client send the first message.

Expected behavior

The server receives connection request immediately after connection.

Additional info

Being able to connect to the server without client sending the first message is useful in server-push-only scenarios. Of course, we can workaround this by having the client send a small message after initiating connection. But it feels wrong to me having to add additional code in order to workaround an issue in a debugging tool.

Originally created by @DL444 on GitHub (Mar 12, 2021). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/815 Originally assigned to: @NghiaTranUIT on GitHub. ### Proxyman version? (Ex. Proxyman 1.4.3) 2.19.0 ### macOS Version? (Ex. mac 10.14) 11.2.3 ### Steps to reproduce 1. First test without Proxyman running. 2. Visit https://www.piesocket.com/websocket-tester 3. Click *Connect*. 4. Note that immediately after connecting you will receive an initial message that looks like `{"info":"You are using a test api key"}`. This means the server has received your connection request. 5. Disconnect from server. 6. Setup Proxyman proxy and enable TLS decryption for `demo.websocket.me` 7. Click *Connect* again. 8. The WebSocket request shows up in Proxyman with a yellow indicator. Note that the initial message previously received is not shown. 9. Wait for a moment to confirm that the request stays in this state indefinitely. 10. Click *Send* to send a message. 11. The request indicator in Proxyman turns green, the initial message appears, and the server echos your message. This proves that the server will not receive connection request before the client send the first message. ### Expected behavior The server receives connection request immediately after connection. ### Additional info Being able to connect to the server without client sending the first message is useful in server-push-only scenarios. Of course, we can workaround this by having the client send a small message after initiating connection. But it feels wrong to me having to add additional code in order to workaround an issue in a debugging tool.
kerem 2026-03-03 19:22:06 +03:00
kerem commented 2026-03-03 19:22:07 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Mar 13, 2021):

Thanks for the detailed input. We will look at it this week and send you a beta build asap 👍

<!-- gh-comment-id:797850712 --> @NghiaTranUIT commented on GitHub (Mar 13, 2021): Thanks for the detailed input. We will look at it this week and send you a beta build asap 👍
kerem commented 2026-03-03 19:22:07 +03:00
Author
Owner
Copy link

@BenTilbrook commented on GitHub (Mar 17, 2021):

I have a similar problem. Can you send me a beta build to test also?

<!-- gh-comment-id:801464341 --> @BenTilbrook commented on GitHub (Mar 17, 2021): I have a similar problem. Can you send me a beta build to test also?
kerem commented 2026-03-03 19:22:07 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Mar 18, 2021):

Sorry to hear that. I was super busy last week with other features. I'm on it now 😄

<!-- gh-comment-id:801525330 --> @NghiaTranUIT commented on GitHub (Mar 18, 2021): Sorry to hear that. I was super busy last week with other features. I'm on it now 😄
kerem commented 2026-03-03 19:22:07 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Mar 20, 2021):

Hey @BenTilbrook and @DL444 Sorry for the delay. Here is the beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_2.20.0_Bug_Websocket.dmg

The reason was Proxyman only makes a WS connection to the destination server as soon as it receives the first WS message from the client. It's wrong and causes the bug.

I fixed it. Proxyman should connect to the server as soon as it's a WS/WSS.

Screen_Shot_2021-03-20_at_14_15_44
<!-- gh-comment-id:803268473 --> @NghiaTranUIT commented on GitHub (Mar 20, 2021): Hey @BenTilbrook and @DL444 Sorry for the delay. Here is the beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_2.20.0_Bug_Websocket.dmg The reason was Proxyman only makes a WS connection to the destination server as soon as it receives the first WS message from the client. It's wrong and causes the bug. I fixed it. Proxyman should connect to the server as soon as it's a WS/WSS. <img width="2163" alt="Screen_Shot_2021-03-20_at_14_15_44" src="https://user-images.githubusercontent.com/5878421/111863142-4e7a5980-898c-11eb-8c3a-5c84a68dbd1a.png">
kerem commented 2026-03-03 19:22:07 +03:00
Author
Owner
Copy link

@DL444 commented on GitHub (Mar 20, 2021):

@NghiaTranUIT
I can confirm that the problem is now fixed.

<!-- gh-comment-id:803271937 --> @DL444 commented on GitHub (Mar 20, 2021): @NghiaTranUIT I can confirm that the problem is now fixed.
kerem commented 2026-03-03 19:22:07 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Mar 20, 2021):

Thanks. I will ship this fix in the next release 🙌

<!-- gh-comment-id:803272133 --> @NghiaTranUIT commented on GitHub (Mar 20, 2021): Thanks. I will ship this fix in the next release 🙌
kerem commented 2026-03-03 19:22:08 +03:00
Author
Owner
Copy link

@DL444 commented on GitHub (Mar 24, 2021):

Since the fix is now publicly released, I think it might be a good time to close this issue.

<!-- gh-comment-id:805988299 --> @DL444 commented on GitHub (Mar 24, 2021): Since the fix is now publicly released, I think it might be a good time to close this issue.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
6.9.0
6.8.0
6.7.0
6.6.0
6.5.0
6.4.0
6.3.0
6.2.0
6.1.0
6.0.2
6.0.0
6.0.1
5.25.0
5.24.0
5.23.0
5.23.1
5.22.0
5.20.0
5.21.0
5.19.0
5.18.0
5.17.0
5.16.0
5.15.0
5.14.0
5.12.2
5.12.1
5.12.0
5.11.0
5.10.0
5.8.0
5.9.0
5.7.0
5.6.1
5.6.0
5.5.0
5.4.0
5.2.0
5.3.0
5.1.1
5.0.0
4.16.0
4.15.0
4.14.0
4.13.0
4.12.0
4.11.0
4.10.0
4.9.1
4.9.0
4.8.2
4.8.1
4.8.0
4.7.1
4.7.0
4.6.1
4.6.0
4.5.0
4.4.0
4.3.1
4.3.0
4.2.1
4.2.0
4.1.0
4.0.0
3.15.0
3.14.0
3.13.0
3.12.0
3.11.0
3.10.0
3.9.0
3.8.0
3.7.0
3.6.2
3.6.1
3.6.0
3.5.2
3.5.1
3.5.0
3.4.0
3.3.0
3.2.0
3.1.0
3.0.0
2.35.4
2.35.3
2.35.2
2.35.1
2.35.0
2.34.1
2.34.0
2.33.0
2.32.1
2.32.0
2.31.0
2.30.0
2.29.0
2.28.0
2.27.0
2.26.0
2.25.0
2.24.0
2.23.0
2.22.0
2.21.1
2.21.0
2.20.0
2.19.0
2.18.0
2.17.0
2.16.1
2.16.0
2.15.2
2.15.1
2.15.0
2.14.2
2.14.1
2.14.0
2.13.0
2.12.0
2.11.1
2.11.0
2.10.0
2.9.1
2.9.0
2.8.0
2.7.0
2.6.0
2.5.3
2.5.2
2.5.1
2.5.0
2.4.2
2.4.1
2.4.0
2.3.0
2.2.0
2.1.1
2.1.0
2.0.1
2.0.0
1.24.0
1.23.0
1.22.0
1.21.0
1.20.0
1.19.0
1.18.1
1.18.0
1.17.1
1.17.0
1.16.0
1.15.0
1.14.1
1.14.0
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.3
1.9.2
1.9.1
1.9.0
1.8.0
1.7.2
1.7.1
1.7.0
1.6.2
1.6.1
1.6.0
1.5.1
1.5.0
1.4.7
1.4.6
1.4.5.1
1.4.5
1.4.4.1
1.4.4
1.4.3
1.4.2
1.4.1.1
1.4.1
1.4
1.3.9
1.3.8
1.3.7
1.3.6
1.3.5
1.3.4.3
1.3.4.2
1.3.4.1
1.3.4
1.3.3
1.3.2
1.3.1
1.3
1.2
1.1.2
1.1.1
1.1
1.0.3
1.0.2
1.0
0.8.1
0.8
0.7
0.6
0.5.1
0.5
v0.4.1
Labels
Clear labels   
Discussion

   
Feature request

   
In Progress...

   
Plugins

   
Waiting response

   
Windows

   
Windows

   
bug

   
duplicate

   
enhancement

   
feature

   
good first issue

   
iOS

   
macOS 10.11

   
question

   
wontfix

   
✅ Done
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Proxyman#810
No description provided.