as a reverse proxy because
the developer of web gateway recommended that due to Nginx works better with
websockets rather than apache.
I was reading that is possible to run apache and nginx in the same port but
changing the listening ip addresses, but is possible to use Nginx as reverse
proxy with apache
On 4 Apr 2014 01:57, sean_at_stitcher nginx-fo...@nginx.us wrote:
I'm not sure I understand why apache wants to renegotiate with nginx, nor
why nginx doesn't seem to want to do it (despite apache thinking it can.)
I vaguely recall seeing (on this list) the suggestion that Apache does this
(at
Brilliant! Thanks so much, I was pulling my hair out on this one. Just
goes to show you... never rely on the apache documentation!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,248982,249012#msg-249012
___
nginx mailing list
My goal is end-to-end encryption of multiple domains using nginx as a
reverse proxy to load balance to multiple backends. Both nginx and apache
use the same wildcard cert, eg *.domain.com.
The first request to https://abc.domain.com/ works as expected, but a call
to https://xyz.domain.com
