Yeah, you are right. I got mixed up because we *talked* about supporting 
generic log tags via header-rewrite in the past. 
Looks like that support was never added.
    On Wednesday, November 18, 2020, 02:51:33 PM PST, Shu Kit Chan 
<chanshu...@gmail.com> wrote:  
 
 I don't think this will work.

Prior to 9.x , header rewrite plugin supports a fixed set of string
substitutions. e.g. %<port>, %<chi>
But it is never for generic log tag. And i think this style of string
substitutions are deprecated after 9.x

In fact, I don't think there are APIs for plugin to get these log tag
values per request in a generic fashion.

Kit



On Wed, Nov 18, 2020 at 1:53 PM Susan Hinrichs
<shinr...@verizonmedia.com.invalid> wrote:
>
> Hmm, I wasn't aware you could access log tags from header-rewrite.
>
> On Wed, Nov 18, 2020 at 3:28 PM Sudheer Vinukonda
> <sudheervinuko...@yahoo.com.invalid> wrote:
>
> >  New API sounds reasonable.
> > For the use case in question though, it may be possible to use
> > header-rewrite rules to achieve this using the log tag 'sstc'
> > Not 100% sure, but something like this might (I haven't tested it) work?
> > cond %{SEND_RESPONSE_HDR_HOOK}
> > cond %<sstc> =10set-header Connection close
> >
> >
> >    On Wednesday, November 18, 2020, 12:15:02 PM PST, 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.
> >
  

Reply via email to