Welcome! Log In Create A New Profile

Advanced

haproxy 1.8 headers ordering issue in logs

Posted by Haim Ari 
Haim Ari
haproxy 1.8 headers ordering issue in logs
December 04, 2017 09:50AM
Hello,


After upgrading to v1.8 we noticed an issue with the headers ordering in the logs,

Here is what i mean:


capture request header User-Agent len 128
capture request header Referer len 64
capture request header Host len 64
capture request header X-Forwarded-For len 64
capture request header True-Client-IP len 500
capture request header X-EdgeConnect-Session-Id len 500
capture request header X-StartApp-Info len 500

These headers are sent correctly to the backends, i can see that in "Tcpdump"
However they are not sent correctly in the logs (syslog)

rolling back to haproxy 1.7.9 with the same configs solves the problem
upgrading again to 1.8 brings back the issue... same goes to 1.9-dev

Can you please advise ?
Thank you,





Haim Ari / SysOps Manager

M: 972.584563032 / T: 972.722288367



[https://www.startapp.com/wp-content/uploads/2017/11/signature-250-1.jpg] https://goo.gl/R83eLy
Christopher Faulet
Re: haproxy 1.8 headers ordering issue in logs
December 04, 2017 11:20AM
Le 04/12/2017 à 09:42, Haim Ari a écrit :
> Hello,
>
>
> After upgrading to v1.8 we noticed an issue with the headers ordering in
> the logs,
>
> Here is what i mean:
>
>
>     capture request header User-Agent len 128
>     capture request header Referer len 64
>     capture request header Host len 64
>     capture request header X-Forwarded-For len 64
>     capture request header True-Client-IP len 500
>     capture request header X-EdgeConnect-Session-Id len 500
>     capture request header X-StartApp-Info len 500
>
> These headers are sent correctly to the backends, i can see that in
> "Tcpdump"
> However they are not sent correctly in the logs (syslog)
>
> rolling back to haproxy 1.7.9 with the same configs solves the problem
> upgrading again to 1.8 brings back the issue... same goes to 1.9-dev
>
> Can you please advise ?
> Thank you,
>

Hi,

I quickly checked and everything works as expected. I used a very simple
configuration with only your "capture request" lines. By reading the
code, I didn't see anything suspicious. Could you share your entire
configuration please (remove all sensitive info, of course) ?

--
Christopher Faulet
Haim Ari
Re: haproxy 1.8 headers ordering issue in logs
December 04, 2017 02:20PM
Hello,


You are right,

I checked again and found the issue, which was haproxy configuration


Running 1.8.1 and it looks ok


Thank you for your help





Haim Ari / SysOps Manager

M: 972.584563032 / T: 972.722288367





________________________________
From: Christopher Faulet <[email protected]>
Sent: Monday, December 4, 2017 12:08 PM
To: Haim Ari; haproxy@formilux.org
Subject: Re: haproxy 1.8 headers ordering issue in logs

Le 04/12/2017 à 09:42, Haim Ari a écrit :
> Hello,
>
>
> After upgrading to v1.8 we noticed an issue with the headers ordering in
> the logs,
>
> Here is what i mean:
>
>
> capture request header User-Agent len 128
> capture request header Referer len 64
> capture request header Host len 64
> capture request header X-Forwarded-For len 64
> capture request header True-Client-IP len 500
> capture request header X-EdgeConnect-Session-Id len 500
> capture request header X-StartApp-Info len 500
>
> These headers are sent correctly to the backends, i can see that in
> "Tcpdump"
> However they are not sent correctly in the logs (syslog)
>
> rolling back to haproxy 1.7.9 with the same configs solves the problem
> upgrading again to 1.8 brings back the issue... same goes to 1.9-dev
>
> Can you please advise ?
> Thank you,
>

Hi,

I quickly checked and everything works as expected. I used a very simple
configuration with only your "capture request" lines. By reading the
code, I didn't see anything suspicious. Could you share your entire
configuration please (remove all sensitive info, of course) ?

--
Christopher Faulet
Sorry, only registered users may post in this forum.

Click here to login