On Fri, Mar 01, 2013 at 06:10:32PM -0500, Chris Yang wrote:
Hi Baptiste,
Thanks for your suggestion. I have read that article (a few times
actually), and except for a few timeout settings I lack comparing to the
config in the article, everything else (that matters for websocket) seems
to be
This change makes the crt block of the documentation easier to use
for those not clear on what needs to go in what file, specifically for
those using CAs that require intermediate certificates.
---
doc/configuration.txt | 44 +---
1 files changed, 29
Hi Willy,
I've just sent a simple patch for this (sorry for the delay). While
preparing this, I was not sure what the difference is between the block in
section 5.2 (Server and default-server options) and the main documentation;
it seems in the case of crt the former has the first few sentances
Hello!
What do you guys think?
I meant something similar to nginx's gzip_min_length.
On 07.02.2013, at 15:56, Dmitry Sivachenko trtrmi...@gmail.com wrote:
Hello!
It would be nice to add some parameter min_compress_size.
So haproxy will compress HTTP response only if response size is
I was trying to troubleshoot this with a packet dump on the peer traffic.
The raw tcpdump does not mean anything to me, and Wireshark is decoding it
as Java RMI traffic which isnt much use, and it looks like a binary
protocol.
So I can report that 'peer' traffic is certainly working because when
5 matches
Mail list logo