# \#tune.http.logurilen not working

**URL:** <https://discourse.haproxy.org/t/tune-http-logurilen-not-working/6480>\
**Category:** Help!\
**Created:** [April 15, 2021, 10:40am UTC](https://discourse.haproxy.org/t/tune-http-logurilen-not-working/6480 "2021-04-15T10:40:33Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![nekno](https://avatars.discourse-cdn.com/v4/letter/n/5f8ce5/32.png) [@nekno](https://discourse.haproxy.org/u/nekno)\
**Post date:** [April 15, 2021, 10:40am UTC](https://discourse.haproxy.org/t/tune-http-logurilen-not-working/6480/1 "2021-04-15T10:40:33Z")

</div>

Hi All,

When there is a get request with bigquery some of the portion of that query is not getting logged in haproxy logs.

I have tried to use tune.http.logurilen in global section, increased it from 1024 default to 2048 but there has been no change , the query in logs is getting cut off at the same place.

Tried few other get requests too happens with all.

Please Note : The query however reaches the server correctly intact , the problem is only with logging it completely in haproxy logs

Is there something that i’m missing.

Many Thanks

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [April 15, 2021, 3:58pm UTC](https://discourse.haproxy.org/t/tune-http-logurilen-not-working/6480/2 "2021-04-15T15:58:53Z")

</div>

As mentioned in the [tune.http.logurilen](http://cbonte.github.io/haproxy-dconv/2.2/configuration.html#3.2-tune.http.logurilen) docmentation:

> If you increase this limit, you may also increase the  
> ‘log … len yyy’ parameter. Your syslog daemon may also need specific  
> configuration directives too.  
> You need to increase the `len` parameter of the `log` keyword, which defaults to 1024:

Also see log:  
[http://cbonte.github.io/haproxy-dconv/2.2/configuration.html#3.1-log](http://cbonte.github.io/haproxy-dconv/2.2/configuration.html#3.1-log)

---

<div class="post-metadata">

**Author:** ![nekno](https://avatars.discourse-cdn.com/v4/letter/n/5f8ce5/32.png) [@nekno](https://discourse.haproxy.org/u/nekno)\
**Post date:** [April 20, 2021, 8:56pm UTC](https://discourse.haproxy.org/t/tune-http-logurilen-not-working/6480/3 "2021-04-20T20:56:14Z")

</div>

Hi Lukas

Many thanks for the information after setting the log len it has improved.

However when the query is too large ( In my case the query sent via Get/Post is around 200kb ) Haproxy immediately gives 400 error and doesn’t forward the request to the backend server.

If you could please let me know what parameter i should tweak how to accomodate such big query with out getting 400 error . It would be extremely helpful to me.

Many Many Thanks

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [April 20, 2021, 10:19pm UTC](https://discourse.haproxy.org/t/tune-http-logurilen-not-working/6480/4 "2021-04-20T22:19:29Z")

</div>

You probably need to tune [tune.bufsize](https://cbonte.github.io/haproxy-dconv/2.2/configuration.html#3.2-tune.bufsize)

---

<div class="post-metadata">

**Author:** ![nekno](https://avatars.discourse-cdn.com/v4/letter/n/5f8ce5/32.png) [@nekno](https://discourse.haproxy.org/u/nekno)\
**Post date:** [April 20, 2021, 11:13pm UTC](https://discourse.haproxy.org/t/tune-http-logurilen-not-working/6480/5 "2021-04-20T23:13:29Z")

</div>

Thanks a lot for replying back Lukas

I have set the following in Global section but still getting 400 error . Any suggestions please

tune.bufsize 80000000  
tune.maxrewrite 4000000  
tune.http.maxhdr 25000

---

<div class="post-metadata">

**Author:** ![nekno](https://avatars.discourse-cdn.com/v4/letter/n/5f8ce5/32.png) [@nekno](https://discourse.haproxy.org/u/nekno)\
**Post date:** [April 21, 2021, 1:02am UTC](https://discourse.haproxy.org/t/tune-http-logurilen-not-working/6480/6 "2021-04-21T01:02:15Z")

</div>

One other thing i noticed is when the query is small the header (gameapp.sg.local) is present

When the query is large the header (gameapp.sg.local) is absent in the haproxy logs

Many Thanks

Attached are 2 screen shots

 ![without_header](https://us1.discourse-cdn.com/flex016/uploads/haproxy/original/2X/9/95e1de540890f1af13582a6e3e8ae48875f0b642.jpeg) ![with_header](https://us1.discourse-cdn.com/flex016/uploads/haproxy/original/2X/c/cfea3566b7078a891cba0599dd596879862e1f5d.jpeg)

---

<div class="post-metadata">

**Author:** ![nekno](https://avatars.discourse-cdn.com/v4/letter/n/5f8ce5/32.png) [@nekno](https://discourse.haproxy.org/u/nekno)\
**Post date:** [April 21, 2021, 9:32pm UTC](https://discourse.haproxy.org/t/tune-http-logurilen-not-working/6480/7 "2021-04-21T21:32:08Z")

</div>

Any suggestion please Lukas.

Thanks

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [April 21, 2021, 10:48pm UTC](https://discourse.haproxy.org/t/tune-http-logurilen-not-working/6480/8 "2021-04-21T22:48:39Z")

</div>

> [@nekno](#):
>
> tune.bufsize 80000000  
> tune.maxrewrite 4000000  
> tune.http.maxhdr 25000

Those are insane values, running this in production will probably crash haproxy quickly. Always read the documentation before you use config knobs.

You can use `show errors` on the admin socket to see why a 400 error is emitted.

> [@nekno](#):
>
> the query sent via Get/Post is around 200kb

That can’t be right, exactly which browser always you do send a 200kb long query? This is an extremely bad idea, you need to put this data in the payload.