in the regular configuration, if a single core is used for stable operation, an occasional 503 occurs when the multi-core mode is enabled, and there is no X-Server
response header information.
global
daemon
-sharp 503
-sharp nbproc 12
log 127.0.0.1 local0
defaults
log global
mode http
maxconn 1000000
timeout tunnel 3600s
timeout connect 3s
timeout client 60s
timeout server 60s
listen stats
bind :9000
mode http
stats enable
stats realm Haproxy\ Statistics
stats uri /haproxy_stats
stats auth admin:123
frontend im-proxy
log global
bind *:80
default_backend server
backend server
server web1 127.0.0.1:7002
http-response set-header X-Server web1