Thanks for the reply Hampton.
When you say “outside the scope” - In general, I am having a hard time understanding what is within and outside the scope for Caddy. It all seems pretty arbitrary to me since Caddy has all sorts of plugins to do all sorts of things and to a certain extent depends on whether someone has written a plugin to provide the function in question - IOW, Caddy being a plugin based system - one cannot really tell what is in scope or outside the scope. Its all seems like a moving target.
Coming to the topic of transparent proxies. In a lot of real life enterprise deployments a “transparent” forward proxy is really defined as a “bump in the wire” or MITM proxy (so that security functions can be implemented in the proxy without the need for explicit proxy configuration in the browser). So when Caddy supports a “transparent” proxy mode, I was led to believe that this is what it means. And in fact, it comes close to what I want but for the proxy “to” address being different than the host what was contained in the original request. All I want is that original URL “host” be used in forwarding the request along.
Yes, you are correct - “mitmproxy.org” provides this function. However, I like Caddy in all the other aspects (written in golang, single static binary, is plugin based for easy extensibility, etc) and I do want to use a few other plugins that it offers that mitmproxy does not.
So the question to you and anyone who can help me is, can Caddy’s transparent proxy plugin be enhanced to do mitmproxy like function - if so, any pointers to how best do that would be greatly appreciated.
Thanks in advance.