Francis,
thank you for your reply. It seems I have fixed the issue. However, I just
wanted to say that in stream mode, you can use NGINX as a forward proxy as
well. As you mention, in stream mode, NGINX behaves as a "TCP router" in the
sense that it just relays segments or packets using the correc
nfig
},
}
and in doing so the private server was expecting to talk to the Proxy which
does not work if we are using SSL passthrough. Instead I had to configure
the proxy as:
*httpsCl = http.Client{
Transport: &http.Transport{
Dial: func(network, add
On Fri, Feb 17, 2017 at 02:52:53PM -0500, agforte wrote:
Hi there,
> I have the following setup:
>
> PRIVATE SERVER <--> NGINX <--> PUBLIC SERVER
>
> I need the NGINX server to work as both reverse and forward proxy with SSL
> passthrough.
That's not goin
Hi all,
I have the following setup:
PRIVATE SERVER <--> NGINX <--> PUBLIC SERVER
I need the NGINX server to work as both reverse and forward proxy with SSL
passthrough. I have found online the following configuration for achieving
this (note that for the forward proxy, I send pa
Lukas,
I think you're right. The combination of three may be optimal at this time.
I'll see what I come up with - I hadn't heard of the PROXY protocol before
(was thinking of something similar though). That's made my life plenty
easier!
Thanks mate :-)
Posted at Nginx Forum:
http://forum.nginx
Hi,
> Hi Lukas,
>
> While HAProxy is able to do some of those things (not sure about
> X-FORWARDED-FOR workarounds?)
Yes, haproxy supports and pushes the PROXY protocol for this exact reason.
> I'd still prefer to use NGINX where possible
> (for other reasons, such as PageSpeed support, etc)
Hi Lukas,
While HAProxy is able to do some of those things (not sure about
X-FORWARDED-FOR workarounds?), I'd still prefer to use NGINX where possible
(for other reasons, such as PageSpeed support, etc)
Is NGINX able to do any of the things mentioned in the question?
Specifically, can it sort by
Hi,
> We currently have a backend server that listens for SSL requests, and (using
> SNI) chooses to pass them on to the correct place, or alternatively will
> serve the requested HTTPS.
>
> Our current configuration is slow (not painfully, just slower than we'd
> like), and we figured having NGI
We currently have a backend server that listens for SSL requests, and (using
SNI) chooses to pass them on to the correct place, or alternatively will
serve the requested HTTPS.
Our current configuration is slow (not painfully, just slower than we'd
like), and we figured having NGINX do some of the
