mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-26 00:25:56 +03:00
[GH-ISSUE #228] ws connection close #225
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#225
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @chilikasha on GitHub (Jul 22, 2019).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/228
Originally assigned to: @NghiaTranUIT on GitHub.
Proxyman version?
1.4.6
macOS Version?
10.14
Steps to reproduce
With recent update I noticed the following behavior:
initsocket event, but in logs (android) I see the following:Thus I can't login.
Everything works fine when proxy is disabled, or if to use another proxy tool.
Expected behavior
Get ws response
Screenshots (optional)
@NghiaTranUIT commented on GitHub (Jul 23, 2019):
Hey @akapitoha, Proxyman hasn't supported WS or WSS yet, so it causes your issues.
We're planning that Socket Previewer #182 will support in next 2 versions. The next one is remap feature 🎉 ETA could be 3 weeks.
Thank you a lot
@chilikasha commented on GitHub (Jul 23, 2019):
hi @NghiaTranUIT
but why did it work fine in previous releases of Proxyman?
I didn't mean previewing sockets events (I use just for https for now). I mean that it looks like Proxyman closes socket events (I may be wrong, please correct me) and I can't use the app which I'm testing, can't login, though it worked before 1.4.6 update
@NghiaTranUIT commented on GitHub (Jul 23, 2019):
Hey, sorry to hear that this updated version break your workflow.
As Proxyman 1.4.6 changes the way of handling HTTP socket, so it affect the WS connection too and I wasn't aware of this socket case.
Here is the hotfix for your issue. I deleted the code to disconnect the connection. https://www.dropbox.com/s/vqfiedfhu97rap8/Proxyman_1.4.6.dmg?dl=0
@akapitoha let try 🍺 (If you're Setapp version, I'm able to send you a setapp build too)
@chilikasha commented on GitHub (Jul 23, 2019):
hey @NghiaTranUIT
just tried this build but still experience same issue (see the same log)
is there anything I can do to help you?
@NghiaTranUIT commented on GitHub (Jul 23, 2019):
For now, please use Proxyman 1.4.5.1 (old version) temporary https://proxyman.s3.us-east-2.amazonaws.com/1451/Proxyman_1.4.5.1.dmg
I will take a look closer this tonight. Thank you for patient.
@NghiaTranUIT commented on GitHub (Aug 25, 2019):
Hey @akapitoha, I've released the Proxyman 1.5.0 https://github.com/ProxymanApp/Proxyman/releases/tag/1.5.0
with the fix on WS/WSS socket too. Basically, the WS/WSS socket is still alive and handle properly. Let check it out 🥇 Thank you in advance 👍
@chilikasha commented on GitHub (Aug 27, 2019):
Hey @NghiaTranUIT
thanks a lot for the update! Everything seems to be fine now :)
@NghiaTranUIT commented on GitHub (Aug 28, 2019):
That's awesome man 😍. Thank you @akapitoha