-
Notifications
You must be signed in to change notification settings - Fork 13
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
how to set proxy while replaying #519
Comments
You can try set proxy via HTTP_PROXY environment variable like this: GoReplay itself has no any specific support for proxies, but underlying Go network stack should respect ENV variable mentioned above. |
I have tried, but It doesn't seem work. |
Just to chime in here, https://github.com/buger/goreplay/blob/master/http_client.go#L86-L106 I'm looking to add this in a fork, just something hacky to make it work for my use case. |
There is way to do it which is kind of trickey. you can request the proxy with modified header. For example, |
I am also facing the same problem. Looks like goreplay is not following the http proxy set in environment. |
@mattrobenolt How did you make it work with your fix? Did you replay like this? It didn't workout for me.
|
@nagendra547 I forked goreplay and added support for it. See: https://github.com/mattrobenolt/goreplay/tree/http-proxy I used this in a production setting just fine without any issues. |
@mattrobenolt love it! Can you create a pull request? Thank you! |
@mattrobenolt Thanks ! Let me try it out. For building the binaries are you using this step mentioned https://github.com/buger/goreplay/wiki/Compilation Or building in some different way? |
Yeah, it would have been that. It's been a while, but that seems right. |
Thanks @mattrobenolt . Worked like a charm! :) |
Just released RC2 with this change https://github.com/buger/goreplay/releases/tag/v1.0-rc2 |
I‘d like to replay http request to target web server,meanwhile set proxy to a fuzz proxy(just like fiddler)to gernerate some bad requests, but goreplay seems not support setting http proxy, is there a plan to support this situation?
The text was updated successfully, but these errors were encountered: