On Sat, Jan 25, 2014 at 10:43:28AM +0100, Willy Tarreau wrote: > So we have no other choice but copying the ID into the session or HTTP > transaction, since it's possible to use it several times. At the same > time, I'm wondering if we should not also increment it for new sessions, > because for people who forward non-HTTP traffic, there's no unique counter. > > What I'm thinking about is the following then : > > - increment the global counter on each new session and store it into > the session. > - increment it again when dealing with a new request over an existing > session. > > That way it would count each transaction, either TCP connection or HTTP > request. And since the ID would be assigned to the session, it would > remain stable for all the period where it's needed.
And I'm realizing that it would also make it possible to match the IDs reported in the "show sess" and "show errors" output with the logs and headers transmitted. Willy
