mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-27 17:15:49 +03:00
[GH-ISSUE #1049] [Feature Request] differentiate domains by port #1044
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#1044
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 @Bertrand on GitHub (Oct 27, 2021).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1049
Originally assigned to: @NghiaTranUIT on GitHub.
When developing several http services at once, most services are served by localhost, each on its own port.
In that case, there is no way to pin only the traffic on one port, and all requests end-up in the same list:
When the list contains dozen of intertwined requests, it's very hard to follow the sequence of requests on a particular service.
It would be great to be able to edit a "pinned" entry and add a port to only see the traffic related to this port.
Of course, we should be able to pin the same domain twice, with a different port.
As for the "Domains" view, Charles Proxy includes the port in domain in Structure View to address this particular point:
This behaviour could be controlled by a global setting.
@NghiaTranUIT commented on GitHub (Oct 27, 2021):
Ah, thanks for pointing it out. It's a small flaw of our current Tree View. Currently, it's grouped by Domain, not the port.
I totally agree that we should the Domain + Port number into the account 👍
To workaround, you might set an alias name (in /etc/hosts) to your localhost service. It will group properly.
I will fix it and send you a beta build soon 🙌
@Bertrand commented on GitHub (Oct 27, 2021):
Many thanks for your quick response.
Please note that there are really two places where this would be useful:
At first, if we could edit the pinned items and add the port, then most of the need would be addressed in a very efficient way.
As for the "Domains" view, I suspect that many people like that the "Domains" view is grouped by domain name, regardless of ports.
A global setting to control "Domains" view behaviour would probably avoid some of your users complaining because of me :) :)
@NghiaTranUIT commented on GitHub (Oct 27, 2021):
For the simplicity, I prefer that 2 same domains with different ports should be in two different groups.
It makes sense if you work on two different localhost servers, such as 127.0.0.1:4000 for React Frontend app, and 127.0.0.1:5000 for the NodeJS Backend. The traffic of each service should be grouped into two groups.
@Bertrand commented on GitHub (Oct 27, 2021):
It is sometimes very useful to see the ordered sequence of calls across all local services.
Thus the option to add a port filtering option on pin entries.
This way you can have 3 different pin entries to address these specific needs
The first two ones let you see service-specific calls
The last one lets you see the overall sequence of calls across all your services.
@Bertrand commented on GitHub (Oct 27, 2021):
But your proposal would already be fantastic BTW :)
@NghiaTranUIT commented on GitHub (Oct 29, 2021):
@Bertrand here is your Beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_2.34.1_Fix_domain_and_port.dmg
Proxyman will display localhost with different ports in separated node 👍
@Bertrand commented on GitHub (Nov 2, 2021):
Hello @NghiaTranUIT.
I've been running on this version for a few days now. No regression found for the moment 👍
And having the traffic well-separated by service is an awesome improvement. Thanks 👏 👏
@NghiaTranUIT commented on GitHub (Nov 2, 2021):
Awesome, glad to hear that 😄 🙌