Re: HTX & tune.maxrewrite [1.9.2]

2019-01-22 Thread Luke Seelenbinder
Hi Christopher, I can confirm the patches fixed the issue. Thanks again for fixing this up! Best, Luke — Luke Seelenbinder Stadia Maps | Founder stadiamaps.com ‐‐‐ Original Message ‐‐‐ On Monday, January 21, 2019 2:07 PM, Christopher Faulet wrote: > Le 18/01/2019 à 14:23, Luke

Re: HTX & tune.maxrewrite [1.9.2]

2019-01-21 Thread Christopher Faulet
Le 18/01/2019 à 14:23, Luke Seelenbinder a écrit : Quick clarification on the previous message. The code emitting the warning is almost assuredly here: https://github.com/haproxy/haproxy/blob/ed7a066b454f09fee07a9ffe480407884496461b/src/proto_htx.c#L3242 not in proto_http.c, seeing how this

Re: HTX & tune.maxrewrite [1.9.2]

2019-01-18 Thread Christopher Faulet
Le 18/01/2019 à 14:23, Luke Seelenbinder a écrit : Quick clarification on the previous message. The code emitting the warning is almost assuredly here: https://github.com/haproxy/haproxy/blob/ed7a066b454f09fee07a9ffe480407884496461b/src/proto_htx.c#L3242 not in proto_http.c, seeing how this

Re: HTX & tune.maxrewrite [1.9.2]

2019-01-18 Thread Luke Seelenbinder
Quick clarification on the previous message. The code emitting the warning is almost assuredly here: https://github.com/haproxy/haproxy/blob/ed7a066b454f09fee07a9ffe480407884496461b/src/proto_htx.c#L3242 not in proto_http.c, seeing how this is in htx mode not http mode. I've traced the issue

HTX & tune.maxrewrite [1.9.2]

2019-01-18 Thread Luke Seelenbinder
Hello all, I just rolled out 1.9.2 compiled from the official tarball to a subset of our servers, and I'm observing some odd behavior in the logs. I'm seeing the following warning (with accompanying warnings about failed hdr rewrites in the stats page): Proxy foo failed to add or set the