On Mon, Jun 07, 2021 at 01:47:44PM -0400, bouvierh wrote:
Hi there,
> I have looked at it, however it looks like this is intended to make proxy
> transparent from upstream/backend perspective:
> It is used so upstream server can see client address not proxy address.
>
> I am looking to do the op
Thanks for the reply!
I have looked at it, however it looks like this is intended to make proxy
transparent from upstream/backend perspective:
It is used so upstream server can see client address not proxy address.
I am looking to do the opposite, I would like to make proxy transparent from
the
On Sat, Jun 05, 2021 at 12:36:47AM -0400, bouvierh wrote:
Hi there,
I don't have a tested answer to your question, but...
> When my application connects to a sever, I am intercepting the request and
> routing it to a nginx process located on the same host (listening to
> 127.0.0.1:8883).
> The i
Hello,
When my application connects to a sever, I am intercepting the request and
routing it to a nginx process located on the same host (listening to
127.0.0.1:8883).
The interception need to be transparent, so IP tables does that well. Now
the issue is restoring the original destination. This wo
