The following config doesn't direct secure websocket connections to the
backend.
What am I doing wrong?
global
log 127.0.0.1 local0
log 127.0.0.1 local1 notice
#log loghostlocal0 info
maxconn 4096
#chroot /usr/share/haproxy
user haproxy
group haproxy
daemon
Is my config reasonable?
On Sun, May 12, 2013 at 6:14 PM, Jonathan Matthews
cont...@jpluscplusm.comwrote:
On 12 May 2013 10:03, pablo platt pablo.pl...@gmail.com wrote:
Can you please explain how to use ssl_fc?
I couldn't find it in the configuration docs.
Please see below the global
secure websockets and RTMP (normal tcp) on the same port.
In the future I'll need normal HTTP requests and static files.
haproxy will pass ssl requests to backend1 and RTMP requests to backend2.
Processes will be open for a long time (minutes - hours).
The backends are on the same machine
On 12 May 2013 10:03, pablo platt pablo.pl...@gmail.com wrote:
Can you please explain how to use ssl_fc?
I couldn't find it in the configuration docs.
Please see below the global and defaults sections which I get when
installing the haproxy-1.4.18 deb package on ubuntu 12.04
ssl_fc is only
Hi,
I need to proxy secure websockets and RTMP (normal tcp) on the same port.
In the future I'll need normal HTTP requests and static files.
haproxy will pass ssl requests to backend1 and RTMP requests to backend2.
Processes will be open for a long time (minutes - hours).
The backends
5 matches
Mail list logo