Where can we find the patch for this to add to src tree of 1.7.10 or any ETA on 1.7.11 including this?
The patch was pushed in HAProxy 1.7 few days ago: http://git.haproxy.org/?p=haproxy-1.7.git;a=commit;h=6917b734023c0de06da2e1c2e31ff63d0358764b
Waiting the next 1.7 release (1.7.11), you can clone the repository or use the right snapshot:
- Latest 1.7 snapshot: http://www.haproxy.org/download/1.7/src/snapshot/haproxy-ss-LATEST.tar.gz
- The first snapshot including the patch: http://www.haproxy.org/download/1.7/src/snapshot/haproxy-ss-20180227.tar.gz
Is there any update on this issue, or an ETA for 1.7.11? We appear to also be experiencing this issue.
HAProxy 1.7.11 was released this morning. Sorry for the delay.
@capflam was this fix ported to 2.1.4 ?
No backport needed, this was commit during 1.8 development, so all 1.8 releases and later have this bugfix, the only backport needed was regarding the 1.7 release more than 2 years ago.
thanks for confirming
Hi,
I’m experiencing this issue, or similar, with version 2.0.27. I’ve noticed there are others topics with 504 and sR termination_state. Not sure if it’s a bug or most probably a misconfiguration.
Full config:
_version=1529
Dataplaneapi managed File
changing file directly can cause a conflict if dataplaneapi is running
global
daemon
chroot /var/lib/haproxy
user haproxy
group haproxy
master-worker
nbproc 1
nbthread 2
cpu-map auto:1/1-2 0-1
maxconn 100000
stats socket /run/haproxy/admin.sock user haproxy group haproxy mode 660 level admin
stats timeout 2m
tune.ssl.default-dh-param 2048
tune.ssl.cachesize 1000000
ssl-default-bind-options no-sslv3 no-tlsv10 no-tlsv11 no-tls-tickets
ssl-default-bind-ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
ssl-default-server-options no-sslv3 no-tlsv10 no-tlsv11 no-tls-tickets
ssl-default-server-ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
log /dev/log local0 info
description HAP Third Cluster
ca-base /etc/ssl/certs
crt-base /etc/ssl/private
defaults
mode http
maxconn 100000
log global
option httplog
cookie SERVERID indirect nocache insert
no option http-use-htx
option redispatch
option dontlognull
option forwardfor
timeout connect 5s
timeout client 50s
timeout server 50s
retries 3
errorfile 400 /etc/haproxy/errors/400.http
errorfile 403 /etc/haproxy/errors/403.http
errorfile 408 /etc/haproxy/errors/408.http
errorfile 500 /etc/haproxy/errors/500.http
errorfile 502 /etc/haproxy/errors/502.custom.http
errorfile 503 /etc/haproxy/errors/503.custom.http
errorfile 504 /etc/haproxy/errors/504.http
userlist controller
user user password pwd
frontend admin-statistics-frontend
mode http
bind :9099
stats enable
stats uri /
stats realm Haproxy\ Statistics
stats auth stats:stats
stats show-node
stats show-legends
stats refresh 300s
stats admin if TRUE
stats show-desc
frontend http-80-frontend
bind 192.168.10.153:80
redirect scheme https code 301 if !{ ssl_fc }
frontend https-443-frontend
bind 192.168.10.153:443 ssl crt /etc/ssl/certificates/pem/ alpn h2,http/1.1
acl backend-2.domain.com-acl hdr(host) -i backend-2.domain.com
acl backend-1.domain.com-acl hdr(host) -i backend-1.domain.com
acl backend-3.domain.com-acl hdr(host) -i backend-3.domain.com
http-request set-header x-forwarded-proto https
http-request set-header CUSTOM custom
use_backend backend-2.domain.com if backend-2.domain.com-acl
use_backend backend-1.domain.com if backend-1.domain.com-acl
use_backend backend-3.domain.com if backend-3.domain.com-acl
backend backend-1.domain.com
mode http
balance roundrobin
option httpchk GET http://backend-1.domain.com/health/ping
server server1 server1:8021 enabled check weight 1 cookie cookie1
server server2 server2:8021 enabled check weight 1 cookie cookie2
backend backend-2.domain.com
mode http
balance roundrobin
server server3 server3:8022 enabled check weight 1 cookie cookie3
server server4 server4:8022 enabled check weight 1 cookie cookie4
backend backend-3.domain.com
mode http
balance roundrobin
option httpchk GET http://backend-3.domain.com/health/ping
server server5 server5:5561 enabled check weight 1 cookie cookie5
server server6 server6:5561 enabled check weight 1 cookie cookie6
Lgs:
[08/Mar/2022:08:46:32.125] https-443-frontend~ backend-1.domain.com/server1 0/0/0/185/50188 200 41814 - - --VN 186/185/59/29/0 0/0 “POST /api/V1/Path/Op HTTP/1.1”
…
[08/Mar/2022:08:47:59.009] https-443-frontend~ backend-1.domain.com/server1 0/0/0/-1/0 504 195 - - sRVN 200/199/59/30/0 0/0 “POST /api/V1/Path/Op HTTP/1.1”
Hope anyone can help me, thanks in advance.