-
Notifications
You must be signed in to change notification settings - Fork 30
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
Released gor1.3 forwards the same request twice on Linux #989
Comments
anatoly71
changed the title
Released gor1.3 forwards the same requests twice on Linux
Released gor1.3 forwards the same request twice on Linux
Aug 11, 2021
buger
added a commit
that referenced
this issue
Aug 12, 2021
Issue was introduced while fixing windows c9274ac Added exception for Windows, which by default allows interfaces without IPs. Interface name check moved higher, so if interface namee or IP match, rest of check will be ignored. Additionally windows npcap loopback mechanism can now be picked by specifying 127.0.0.1 or loopback IP. Fix #989
buger
added a commit
that referenced
this issue
Aug 12, 2021
Issue was introduced while fixing windows c9274ac Added exception for Windows, which by default allows interfaces without IPs. Interface name check moved higher, so if interface namee or IP match, rest of check will be ignored. Additionally windows npcap loopback mechanism can now be picked by specifying 127.0.0.1 or loopback IP. Fix #989
Should be fixed now and released as 1.3.1! |
I've tested 1.3.1 on Linux and the issue is fixed. Thanks a lot! |
xingren23
referenced
this issue
in xingren23/goreplay
Sep 4, 2021
Issue was introduced while fixing windows buger/goreplay@c9274ac Added exception for Windows, which by default allows interfaces without IPs. Interface name check moved higher, so if interface namee or IP match, rest of check will be ignored. Additionally windows npcap loopback mechanism can now be picked by specifying 127.0.0.1 or loopback IP. Fix #989
xingren23
referenced
this issue
in xingren23/goreplay
Sep 4, 2021
Issue was introduced while fixing windows buger/goreplay@c9274ac Added exception for Windows, which by default allows interfaces without IPs. Interface name check moved higher, so if interface namee or IP match, rest of check will be ignored. Additionally windows npcap loopback mechanism can now be picked by specifying 127.0.0.1 or loopback IP. Fix #989
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, I am using macbook, gor1.3.
I deploy two docker containers (linux) exposing an http endpoint each.
They are started with docker-compose so that they can communicate with each other being on the same docker network.
"mock1" linux container:
./gor1.3 -verbose 3 -input-raw :9003 -output-http http://mock2:9004
"mock2" linux container:
I execute tcpdump on the both containers to see requests.
Scenario:: mac host -> linux mock1 (goreplay) -> linux mock2.
I send a request to linux container mock1 (goreplay here) using mapped port 9093, and I expect the request forwarded to linux container mock2. The actual outcome TWO requests forwarded.
on my workstation I execute
curl -v "http://localhost:9093/some/path" -H "accept: application/json"
mock1
tcpdump records ONE incoming request but goreplay reports TWO incoming requests
goreplay reports TWO incoming requests (same meta data in the debug output)
mock2
TWO requests received
The text was updated successfully, but these errors were encountered: