Re: Trying to get logging above 1024 characters

On 8/14/2018 3:06 PM, Cyril Bonté wrote: >> Is there any config that will successfully log the full request? > > Please read the documentation about the length option for the log > keyword, particularly the part about tune.http.logurilen ;-) Thank you! That fixed it, I'm now successfully logging

Re: Trying to get logging above 1024 characters

Hi Shawn, Le 14/08/2018 à 22:53, Shawn Heisey a écrit : I'm trying with 1.8.13 to get full logging of requests that would push the syslog message beyond 1024 characters. I'm not having very good luck. I have this config in global: log 127.0.0.1 len 65535 format rfc5424 local0 log 127.

Trying to get logging above 1024 characters

I'm trying with 1.8.13 to get full logging of requests that would push the syslog message beyond 1024 characters. I'm not having very good luck. I have this config in global: log 127.0.0.1 len 65535 format rfc5424 local0 log 127.0.0.1 len 65535 format rfc5424 local1 notice In some of th

[PATCH] DOC: dns: explain set server ... fqdn requires resolver

Abhishek Gupta reported on discourse that set server [...] fqdn always fails. Further investigation showed that this requires the internal DNS resolver to be configured. Add this requirement to the docs. Must be backported to 1.8. --- doc/management.txt | 3 ++- 1 file changed, 2 insertions(+), 1

Haproxy 1.8 segfaults on misconfigured set server fqdn command

Hello, the "set server / fqdn " admin socket command requires the internal DNS resolver to be configured and enabled for that specific server. This is undocumented, and I will provide a doc fix soon. However, when the resolver is not configured, and when haproxy is compiled with thread support,