Skip to content
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

Can GoReplay capture HTTPS traffic in port 443? #1218

Open
stefanie0722 opened this issue Aug 3, 2023 · 2 comments
Open

Can GoReplay capture HTTPS traffic in port 443? #1218

stefanie0722 opened this issue Aug 3, 2023 · 2 comments

Comments

@stefanie0722
Copy link

Currently we use Nginx ngx_mirror_module to implements mirroring of original HTTPS request and pass to other local port like 8081. So that Goreplay can capture this traffic in port 8081.
But we have a concern that the mirroring in Nginx may have an impact on system performance while pressure testing, because lots of requests might cause the mirroring also take many system resource.
So, is there any solution for GoReplay to capture the HTTPS traffic without modification on reverse-proxy nodes?
Thanks!

@crylg
Copy link

crylg commented Jun 13, 2024

mark

@gitSambhal
Copy link

Try

gor --input-raw :8081 --input-raw-engine "raw_socket" --output-http "http://staging.com"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants