In this scenario they would set "Connection: close" in the request header.
I am assuming they don't have the control over the origin to make this change there. Or it is always easier to hassle the proxy folks to get these things done :-) On Wed, Nov 18, 2020 at 2:39 PM Shu Kit Chan <chanshu...@gmail.com> wrote: > Actually I was thinking about this question a bit. 2 points to make. > > 1) I am Ok with the naming convention > > 2) So the origin wants to be the one to set "Connection: close" in the > response. Wouldn't the origin also has that piece of information > (transaction count) to make that decision? May be their application > framework/platform doesn't allow them to easily get that? > > > On Wed, Nov 18, 2020 at 12:31 PM Shu Kit Chan <chanshu...@gmail.com> > wrote: > > > > I think you mean the existing one is TSHttpSsnTransactionCount . Right ? > > > > > > On Wed, Nov 18, 2020 at 12:15 PM Susan Hinrichs > > <shinr...@verizonmedia.com.invalid> wrote: > > > > > > I propose int TSHttpTxnServerSsnTransactionCount(TSHttpTxn txn) as an > > > addition to the InkAPI. It returns the number of transactions that > have > > > been performed on the server session currently associated with the txn. > > > This would be analogous to the TSHttpTxnServerSsnTransactionCount > function > > > which returns the same information for the user agent session. The > > > TSHttpTxnServer prefix seems to be used in other InkAPI calls dealing > with > > > the server transaction/session associated with the HttpSM. > > > > > > We have a customer that would like to add a "Connection: close" header > to > > > the server request after a certain number of requests have been made > on the > > > connection. If there is an existing way to do this, I'd be interested > to > > > know that too. >
