-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mixup of localhost ports between multiple requests #2164
Comments
@perhells may I if you're using any debugging tools that can change the port number? like Scripting or Map Remote? or Reverer Proxy? |
Hi! No, we're not using any other debugging tool. I'm using the "Proxyman Helper Tool" only, otherwise no outgoing requests from our Go application shows up at all: https://docs.proxyman.io/troubleshooting/i-couldnt-see-any-traffics-on-proxyman#id-2.3-install-proxyman-helper-tool Edit: Added detail about using Go and Proxyman Helper Tool to issue. |
Description
Ports are mixed together if connecting to multiple services using localhost in a Go application.
Steps to Reproduce
We're running an application using multiple forwarded ports due to our services residing inside a VPC using internal load balancers. A part of our configuration used to access these by using port forwarding to an ECS task in our application looks like this:
http://localhost:32003
-> Service Ahttp://localhost:32004
-> Service BThen in our local application we use the following environment configuration:
Our application works as intended with this setup, but we cannot inspect the outgoing requests since Proxyman doesn't catch them (at least not on macOS).
This can be solved by adding an entry to
/etc/hosts
:If we then change our URLs in the application environment from
localhost
toproxyman.debug
we can see the requests in Proxyman. Doing this for one service works perfectly:Current Behavior
When we try to use the
proxyman.debug
URL for both services like this we run into an issue:The service A requests looks correct:
But the ports are somehow mixed up for service B requests:
We tried adding two different mappings to make Proxyman think these were different endpoints as well:
But this still results in the same issue:
Expected Behavior
We expect Proxyman to be able to correctly route these requests to the correct localhost/proxyman.debug port.
Environment
The text was updated successfully, but these errors were encountered: