Thanks Willy! That worked perfectly.
Phil
On Fri, Sep 1, 2017 at 1:12 PM, Willy Tarreau <w...@1wt.eu> wrote:
> Hi Philip,
>
> On Fri, Sep 01, 2017 at 09:28:50AM -0400, Philip Seidel wrote:
> > Is there a maximum length when using capture.req.uri? It appears that
> th
Is there a maximum length when using capture.req.uri? It appears that the
value is truncated when approaching close to 1024 bytes. It appears to be
1020 from the tests I was running. I have attempted to reduce
tune.maxrewrite to 1024 since tune.bufsize is 16k; however, it appears that
this
Thanks for the help everyone. I have tested out the patches and I no
longer see any memory being leaked. How long does it take before an
official release will be cut?
Thanks,
Phil
On Wed, Apr 26, 2017 at 9:13 AM, Willy Tarreau wrote:
> On Wed, Apr 26, 2017 at 03:12:11PM +0200,
aroud.
> I try to understand the memleak.
>
> Thierry
>
>
> On Wed, 26 Apr 2017 12:11:16 +0200
> Thierry Fournier <thierry.fourn...@arpalert.org> wrote:
>
> > Hi,
> >
> > Thanks for the bug report. I can reproduce the bug.
> > I will look for a fix.
Possible Lua Memory Leak?
We are running HAProxy version 1.7.2 (also tested 1.7.5) and are loading a
Lua file which makes use of 2 actions. The first action is called on
http-request and the second on http-response. In the simple test case we
put together the request action stores some data in
5 matches
Mail list logo