Re: no-sslv3 in default

Hello I'd go further. Sslv3 us an obsolete protocol does anyone disagree with that? For a start make no-sslv3 the default and have a enable-obsolete-sslv3 option. Or better make enabling it a compile time option. Or maybe just get rid of it altogether? The examples on the web and on this

Re: no-sslv3 in default

Hi, 2014-10-16 10:34 GMT+02:00 Neil - HAProxy List maillist-hapr...@iamafreeman.com: I'd go further. Sslv3 us an obsolete protocol does anyone disagree with that? For a start make no-sslv3 the default and have a enable-obsolete-sslv3 option. Or better make enabling it a compile time

is it possible to SSL offloading and then re-pack as SSL?

I want to do haproxy 1.5 SSL offloading, filter/processing some headers and then re-send as SSL? thanks, Robert

Re: Segmentation fault with version 1.5.5

On Thu, Oct 16, 2014 at 12:10:32AM +0200, Marco wrote: Hi Cyril, Did you perform a make clean before compiling haproxy 1.5.5 ? Thanks for the hint! Indeed, that was the error. Recompiling with make TARGET=linux2628 ARCH=native USE_OPENSSL=yes clean all helped. Works like a charm now.

Re: is it possible to SSL offloading and then re-pack as SSL?

Hi, On 16.10.2014 22:36, Lukas Tribus wrote: I want to do haproxy 1.5 SSL offloading, filter/processing some headers and then re-send as SSL? Yes, it is. Lukas Have a look at http://blog.haproxy.com/2013/02/26/ssl-offloading-impact-on-web-applications/

Switching Java client to Websocket with SSL // Connection closed during SSL handshake

Hello, Due to connection limit problems I´d like to remove stunnel from a configuration in front of haproxy. The original setup was: - stunnel was responsible for the SSL(https) connection - using localhost the web traffic was transferred to haproxy - haproxy divided traffic into web page

RE: Switching Java client to Websocket with SSL // Connection closed during SSL handshake

Hi Heiko! Due to connection limit problems I´d like to remove stunnel from a configuration in front of haproxy. The original setup was: - stunnel was responsible for the SSL(https) connection - using localhost the web traffic was transferred to haproxy - haproxy divided traffic into web

Understanding haproxy cpu usage in ssl-offload scenario

Hi, I'm currently trying to determine the best configuration for haproxy but have issues with understanding how the cpu's are used. The system is a virtual machine configured with 8 cores. The global section of the configuration contains these cpu settings: nbproc 8 cpu-map all