haproxy 1.8 headers ordering issue in logs

Mon, 04 Dec 2017 00:44:01 -0800 

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>

Reply via email to