haproxy: http-send-name-header no longer needed

- destination server gets its own server id - this removes complexity at the cost of respecting consistency in names

haproxy: http-send-name-header no longer needed
- destination server gets its own server id - this removes complexity at the cost of respecting consistency in names
e14bf5ab · Roque · ebb0421a · e14bf5ab · e14bf5ab
Commit e14bf5ab authored Apr 19, 2018 by Roque
Show whitespace changes
Inline Side-by-side

Showing with 1 addition and 2 deletions

stack/erp5/buildout.hash.cfg stack/erp5/buildout.hash.cfg +1 -1

stack/erp5/haproxy.cfg.in stack/erp5/haproxy.cfg.in +0 -1

No files found.
--- a/stack/erp5/buildout.hash.cfg
+++ b/stack/erp5/buildout.hash.cfg
@@ -95,4 +95,4 @@ md5sum = 29cfe35d37cf615378574707978e5f75

 [template-haproxy-cfg]
 filename = haproxy.cfg.in
-md5sum = 3defd473e2cea17ae36bba7752494858
+md5sum = 13f1f731ec941f4ba941d6fa8834a5cc
--- a/stack/erp5/haproxy.cfg.in
+++ b/stack/erp5/haproxy.cfg.in
@@ -12,7 +12,6 @@ defaults
  option redispatch
  maxconn 2000
  cookie SERVERID rewrite
-  http-send-name-header X-Balancer-Current-Server
  balance roundrobin
  stats uri /haproxy
  stats realm Global\ statistics