Hi.
On 31.01.22 16:51, Roberto Carna wrote:
Dear all, I have haproxy-1.5.18-3.el7.x86_64 running OK.
You should consider to use a maintained version as 1.5 is End of Life from the
community.
https://www.haproxy.org/
https://github.com/DBezemer/rpm-haproxy
Development area are claiming for an error, after clicking on a given URL from
an internal App. We have
two backends nodes, and when DEV tries pointing to just one node, the click is
OK. So we thought it was
a persistent session problem, so we set up a cookie. The sessions now are
persistent for the clients, it
is OK, but when DEV tests the click with the problem, effectively it occurs
again This is in haproxy.log
for this error:
10.10.1.14:59016 [31/Jan/2022:12:33:18.649] Port_443_lbb1~ Port_443_lbb1/*<NOSRV>*
-1/-1/-1/-1/2232 *400* 187 - - PR-- 3/3/0/0/0 0/0 {|} "<*BADREQ*>"
10.10.1.14:59019 [31/Jan/2022:12:33:15.579] Port_443_lbb1~ app/NODE1 5824/0/0/54/5878 204
610 - - --VN 3/3/0/1/0 0/0 {|app.company.com} "POST /api/data/UpdateRecentItems
HTTP/1.1"
The backend is the following:
backend APP
balance roundrobin
cookie SERVERID insert
server NODE1 10.10.18.1:443 check cookie NODE2 ssl verify none
server NODE2 10.10.18.2:443 check cookie NODE2 ssl verify none
If I remove the "check" option from the two lines, the error appears again:
Error 400 - Bad Request - Your browser sent a invalid request.
But when I point the browser to just one node editing the hosts file, the click
works OK.
Please what can be the problem?
Thanks a lot !!!
Well I suggest to run haproxy with "-d" to see what happens as it's dev.
You should also try to use the "Network" view in the Browsers Developer Tools
when you click.
Please also share more of the config as the BADREQ could lead also at the
listen or frontend part.
Regards
Alex
