Since commit 27d93c3f9428 ("BUG/MAJOR: compression/cache: Make it
really works with these both filters"), we no longer use section
deinit_comp_ctx.
This should fix github issue #441
Signed-off-by: William Dauchy
---
src/flt_http_comp.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/src/fl
crt-base is also used after "crt" directive.
Signed-off-by: William Dauchy
---
doc/configuration.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/configuration.txt b/doc/configuration.txt
index d0bb9741..9ac89851 100644
--- a/doc/configuration.txt
+++ b/doc/configu
> On 11 Jan 2020, at 07:48, Willy Tarreau wrote:
>
> On Fri, Jan 10, 2020 at 03:17:59PM -0800, Sadasiva Gujjarlapudi wrote:
>> After applying the patch and socket wasn't `close`d in Lua code
>> request/sec 7898.0976
>> $time haproxy
>> real 0m6.689s
>> user 0m1.043s
>> sys 0m1.059s
>>
>> Afte
Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses t
Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses t
Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses t
Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses t
Hi Wietse,
[CCing haproxy ML and responding inline]
First, thanks a lot for your detailed analysis.
On Sat, Jan 11, 2020 at 09:03:19PM -0500, Wietse Venema wrote:
> I found a portability bug in haproxy's CRC32 implementation, while
> adding adding CRC32 support to Postfix's haproxy2 code. The ha
❦ 9 janvier 2020 20:07 +01, Tim Düsterhus :
> If you would package the haproxy-lua-http library for Debian
> (https://github.com/haproxytech/haproxy-lua-http) [1], what would you
> believe would be most "useful" / "in spirit of Debian packaging" / "your
> choice"?
>
> a) Install the library into
9 matches
Mail list logo
