the haproxy is conforming to the following setup:
http://blog.haproxy.com/2012/04/13/enhanced-ssl-load-balancing-with-server-name-indication-sni-tls-extension/
Look for:
Choose a server using SNI: aka SSL routing
No certificates available to haproxy, so no decoding and/or adding removing
headers
Hello!
On Wed, Nov 23, 2016 at 04:14:23AM -0500, noci wrote:
> I have a strange problem.
>
> Setup:
> Internet ---> haproxy (SNI TLS Routing) --> nginx (Webserver) --> Websocket
> based server (WebRTC)
> haproxy has no certificates, it checks the TLS Hello message for :443
> traffic and then fo
I tried both V1.10.1 and V1.11.6 same behaviour
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,271128,271132#msg-271132
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi,
I have a strange problem.
Setup:
Internet ---> haproxy (SNI TLS Routing) --> nginx (Webserver) --> Websocket
based server (WebRTC)
haproxy has no certificates, it checks the TLS Hello message for :443
traffic and then forwards to the right server based on SNI.
==> haproxy cannot alter the st
