Hello!

I am testing haproxy version 1.9.4 on Ubuntu 18.04.

With the "option http-use-htx", haproxy shows a strange behaviour when the real server is IIS and if the users' browsers try to do a POST.

A configuration similar to the following lets the GETs work properly, but the POST fails after the server timeout (session state "SD" in haproxy logs):

listen tesi-http
  bind 10.64.44.112:443 name HTTPS ssl crt XXX
  option http-use-htx
  server vxws142a-82 11.22.33.44:82

If the connection to the real server is closed, all GETs and POSTs work

listen tesi-http
  bind 10.64.44.112:443 name HTTPS ssl crt XXX
  option http-use-htx
  option http-server-close
  server vxws142a-82 11.22.33.44:82

In other words, it seems that the "option http-use-htx" only works together with "http-server-close" with this real server.

Notes:
. The behaviour does not change if "alpn h2,http/1.1" is added/removed from the "bind" line.
. The behaviour does not change if the browser is firefox or IE
. With tcpdump on the haproxy node I was not able to understand who is waiting for whom :-)
. I am not sure that I can install wireshark on the real server.

Can someone please suggest me what to look for in the IIS or in the haproxy configuration?

Thank you

.marcoc

Reply via email to