Am 21.11.2019 um 08:09 schrieb Alexander Kasantsev:
I updated haproxy to 1.7.12 but nothing changed

Okay that's bad, because I thought this commit will fix your issue.
http://git.haproxy.org/?p=haproxy-1.7.git;a=commit;h=777a0aa4c8a704e06d653aed5f00e6cda2017a4d

Regards
Aleks

20 нояб. 2019 г., в 15:38, Aleksandar Lazic <al-hapr...@none.at> написал(а):


On this page is a 1.7.12 listed, is this the repo which you use?

https://repo.ius.io/6/x86_64/packages/h/

Please can you try the 1.7.12.

Do you know that eol is next year?
https://wiki.centos.org/Download

Regards
Aleks

Nov 20, 2019 12:45:37 PM Alexander Kasantsev <cont...@mrwho.ru>:

I’m on CentOS 6.10, the latest version for me is 1.7.11 from ius repo

20 нояб. 2019 г., в 14:17, Aleksandar Lazic
написал(а):


Hi.

Please can you use the latest 1.7, latest 1.8 or 2.0 and tell us if the problem 
still exist.

Best regards
Aleks

Nov 20, 2019 9:52:01 AM Alexander Kasantsev
:

Good day everyone!

I’m migrated from haproxy 1.5 to 1.7.11 and I have some troubles with logging

I have a following in config file for logging

capture request  header Host len 200
capture request  header Referer len 200
capture request  header User-Agent len 200
capture request  header Content-Type len 200
capture request  header Cookie len 300
log-format %[capture.req.hdr(0),lower]\ %ci\ -\ [%t]\ \"%HM\ %HP\ %HV\"\ %ST\ \"%[capture.req.hdr(3)]\"\ %U\ 
\"%[capture.req.hdr(1)]\"\ \"%[capture.req.hdr(2)]\"\ \"%[capture.req.hdr(4)]\"\ %Tq\ \"%s\"\ 'NGINX-CACHE-- 
"-"'\ \"%ts\»


Logformat is almost the same with Nginx

But is some cases it works incorrectly

For example log output

Nov 20 10:41:56 lb.loc haproxy[12633]: example.com 81.4.227.173 - [20/Nov/2019:10:41:56.095] "GET /piwik.php H" 200 "-" 2396 
"https://example.com/"; "Mozilla/5.0" "some.cookie data" 19 "vm06.lb.rsl.loc" NGINX-CACHE-- "-" "—"

Problem is that "GET /piwik.php H"  must be "GET /piwik.php HTTP/1.1"
its %HV parameter in log-format

A part of "HTTP/1.1" randomly cut’s off. It may be "HT" or "HTT" or "HTTP/1."





Reply via email to