Add a 'stats disable' option that can be used to explicitly disable the
stats, without issuing the warning message as seen on TCP proxies.
If any stats options are present in a default block, there is presently
no way to explicitly disable them for a single proxy, other than
defining a new
Hello List,
What is the best practices on getting incremental minutely deltas from
HAProxy stats for metrics like minutely metrics like latency, 2xx/4xx/5xx
requests. My intent is to emit these metrics from individual instances of
HAProxy running across my fleet and send it to AWS Cloudwatch.
On 15/12/2016 19:03, Lukas Tribus wrote:
Hi Igor,
Am 14.12.2016 um 20:47 schrieb Igor Pav:
Hi Lukas, in fact, openssl already gets early TLS 1.3 adoption in dev,
will release in 1.1.1, and BoringSSL supports TLSv1.3 already.
That's nice, and in fact since 1.1.1 will be API compatible with
Hi Lukas,
On Thu, Dec 15, 2016 at 10:47:38PM +0100, Lukas Tribus wrote:
> Hi Willy,
>
>
> Am 05.12.2016 um 19:31 schrieb Willy Tarreau:
> >
> > This extra CRLF marks the end of headers and everything which follows is
> > a body, so nginx does the right thing by not seeing it since it's a bug.
Hi Willy,
Am 05.12.2016 um 19:31 schrieb Willy Tarreau:
This extra CRLF marks the end of headers and everything which follows is
a body, so nginx does the right thing by not seeing it since it's a bug.
I've merged the fix now. I can confirm that the very first commit that
brought this feature
Hi Igor,
Am 14.12.2016 um 20:47 schrieb Igor Pav:
Hi Lukas, in fact, openssl already gets early TLS 1.3 adoption in dev,
will release in 1.1.1, and BoringSSL supports TLSv1.3 already.
That's nice, and in fact since 1.1.1 will be API compatible with 1.1.0
[1] *and* support
TLS 1.3 (or
On Thu, Dec 15, 2016 at 02:43:24PM +0700, Dylan Jay wrote:
> I think the distcc example does sound similar. That is basically whats
> happening here. The time to read from disk + send back is not insignificant,
> but the CPU part is done and is able to handle another request. Not sure if I
>
Hi Conrad!
I hope you're fine.
sorry to revive this very old thread, but I was wondering if there is still
> interest in this, now that the DNS subsystem has been refactored?
>
Of course we do :)
> I was looking at implementing SRV records and noticed that the default UDP
> message size of
8 matches
Mail list logo