> On Jan 16, 2015, at 10:27 AM, Alan M. Carroll <a...@network-geographics.com> > wrote: > > Friday, January 16, 2015, 12:17:35 PM, you wrote: > >> Yeh +1 from me on not firing TXN_START unless it's really HTTP. Though, >> maybe the right approach is to keep the current event timing, but only fire >> TXN_START on HTTP ports? > > We still want to fire that event on HTTP transactions on SSL ports if it's > actually an HTTP transaction. The problem here is that we don't really know > it's HTTP even on an HTTP port until we've parsed the request header and at > that point we've advanced to the READ_REQUEST_HDR state. A plugin may also > want to switch to a blind tunnel before any request is parsed at all, based > on IP addresses. So I think we have to live with TXN_START happening even in > non HTTP cases.
But eventually, the session is handled by a leaf in the acceptor tree. At that point, do we have enough information to know whether to invoke transaction hooks? Maybe blind tunneling is the exception here ... J
