[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.

diff --git a/src/client.c b/src/client.c
index 444d47fb56875ab61a7d2e52f2829b14377ce0ea..be0c90268e1be069a7bccd1d80093267d04933d3 100644 (file)
--- a/src/client.c
+++ b/src/client.c
@@ -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;

diff --git a/src/proto_uxst.c b/src/proto_uxst.c
index 91b394489e16d925cc4d2f84d76cf5366ea5c962..eb4a53dd0094daf2e5529a96a216efe593256d2f 100644 (file)
--- a/src/proto_uxst.c
+++ b/src/proto_uxst.c
@@ -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;