mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-11 22:15:14 +00:00
[BUG] client: always ensure to zero rep->analysers
The response analyser was not emptied upon creation of a new session. In fact it was always zero just because last session leaved it in a zero state, but in case of shared pools this cannot be guaranteed. The net effect is that it was possible to have some HTTP (or any other) analysers on the response path of a stats unix socket, which would reject the response. This fix must be backported to 1.4.
This commit is contained in:
parent
39e4f62186
commit
e29e1c5df4
@ -413,6 +413,7 @@ int event_accept(int fd) {
|
||||
s->rep->prod = &s->si[1];
|
||||
s->rep->cons = &s->si[0];
|
||||
s->si[0].ob = s->si[1].ib = s->rep;
|
||||
s->rep->analysers = 0;
|
||||
|
||||
s->rep->rto = s->be->timeout.server;
|
||||
s->rep->wto = s->fe->timeout.client;
|
||||
|
@ -514,6 +514,7 @@ int uxst_event_accept(int fd) {
|
||||
s->rep->prod = &s->si[1];
|
||||
s->rep->cons = &s->si[0];
|
||||
s->si[0].ob = s->si[1].ib = s->rep;
|
||||
s->rep->analysers = 0;
|
||||
|
||||
s->rep->rto = TICK_ETERNITY;
|
||||
s->rep->cto = TICK_ETERNITY;
|
||||
|
Loading…
Reference in New Issue
Block a user