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
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
fail2ban comes to mind (ipset + iptables + logscanner).
http://www.fail2ban.org/
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,270680,271131#msg-271131
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Log through syslog to another system?
If the other system isn't listening there is no harm done... (Slightly more
network traffic).
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,271108,271130#msg-271130
___
nginx mailing list
nginx@nginx.or
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