Hi Willy, Le 28/10/2013 07:36, Willy Tarreau a écrit :
Good analysis. Indeed, "tcp-request track-sc*" does not wait for anything (eg: for connection we must not wait). It is documented as tracking only what is found. The proper method to wait for contents if needed is to rely on a condition for the track rule to take action :
Oh yes, I better understand the last paragraph for the "tcp-request content" documentation now (probably read it too fast) ;-)
I saw in the code that a condition would wait (that's why i also added a return for the track-sc test) but I didn't realized that the behaviour was documented.
Well, I hope that Przemyslaw's issue is now gone, then. -- Cyril Bonté
