Le 16/01/2018 à 16:18, Lukas Tribus a écrit :
Hello Christopher,
On 16 January 2018 at 15:01, Bart Geesink <[email protected]> wrote:
Hi,
We have an issue in haproxy > 1.8 on CentOS when using SSL in the server
configuration. Haproxy sometimes logs a http status code "-1" followed
by the termination_state SDxx. This happens every few requests. When
using one backend, the clients don't notice it. When using multiple
backends, this can result in redirecting traffic to the wrong backend
(the proxy inserts a cookie to track which backend is used).
Removing the SSL configuration and using plain http solves the issue, as
does downgrading to version 1.7.
Also see:
https://discourse.haproxy.org/t/session-state-sdnn-http-status-code-200-when-upgrading-to-1-7/1409/10
Hi Lukas,
Thanks, I will check these 2 issues. First of all, I need to reproduce
them to be sure. This one seems to be a bit different because the status
code is "-1".
Bart, when you said your backend does not log any problems, it means
that for a request logged with SD termination state on haproxy, you have
a 200 on Apache side ? And what does the response look like from the
client side ? (truncated / good / error ...)
--
Christopher Faulet
