Great! Here is the feedback: https://github.com/saucelabs/forwarder/issues/616
Show HN: Forwarder – FOSS MITM proxy written in Go
11–18 of 18 posts
Re: Show HN: Forwarder – FOSS MITM proxy written in Go
#12Wish this had a caching feature… Setting up squid as a https caching forward proxy in docker is a pain.
Please file an issue, we'll see what we can do.
Re: Show HN: Forwarder – FOSS MITM proxy written in Go
#13Re: Show HN: Forwarder – FOSS MITM proxy written in Go
#14I'm not too versed on these, but why not use nginx?
I haven’t tried to use nginx as an MITM proxy or this project at all, but presumably it’s easier to use this when your usecase lies closer to the client than the server and vice versa.
Re: Show HN: Forwarder – FOSS MITM proxy written in Go
#15I'm not too versed on these, but why not use nginx?
Re: Show HN: Forwarder – FOSS MITM proxy written in Go
#16Great! Here is the feedback: https://github.com/saucelabs/forwarder/issues/616
Re: Show HN: Forwarder – FOSS MITM proxy written in Go
#17Why? Do you have a comparison? Or even a list of your features, beyond the 6 bullet points on your homepage?
Re: Show HN: Forwarder – FOSS MITM proxy written in Go
#18I'm not too versed on these, but why not use nginx?
Tools like Fiddler allow traffic modification based on rules, so you can tamper traffic. Forwarder doesn't appear to allow modification (other than headers?) so I think it's about logging traffic and collecting metrics. Still looking at the docs, I could have missed something.
Here's draft proposal for 1.3 to add this feature https://github.com/saucelabs/forwarder/issues/584.
The idea is to allow users work in JavaScript with Go http.Request and http.Request. Interop between Go and JS in Goja is very good.