Thanks Willy! That worked perfectly. Phil
On Fri, Sep 1, 2017 at 1:12 PM, Willy Tarreau <[email protected]> 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 > 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 doesn't have any impact. Are there some other settings that need to > > be adjusted to ensure that the value is not truncated? > > It was made configurable very recently in 1.8-dev but it's not backported. > Instead you may apply the other solution documented in the commit message : > > commit 23e9e931284b44e9d06cca26ab13648873b4029b > Author: Stéphane Cottin <[email protected]> > Date: Thu May 18 08:58:41 2017 +0200 > > MINOR: log: Add logurilen tunable. > > The default len of request uri in log messages is 1024. In some use > cases, you need to keep the long trail of GET parameters. The only > way to increase this len is to recompile with DEFINE=-DREQURI_LEN=2048. > > This commit introduces a tune.http.logurilen configuration directive, > allowing to tune this at runtime. > > Hoping this helps, > Willy >
