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
by SNI hostname without becoming an SSL endpoint?
If not, is there a reason why? (has it been decided by the community that
it's not a good idea, or it just hasn't been developed?)
I've seen a few similar questions around, but no definitive answer.
Thanks,
OzJD
Posted at Nginx Forum:
http
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:
