You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by po...@gmail.com on 2014/07/12 05:39:36 UTC
回复： Using TSHttpTxnServerIntercept() prevents logging?
I did not have this problem as our trafficserver is based on 3.2, I don’t know whether there is something changed.
I think both TSHttpTxnIntercept() and TSHttpTxnServerIntercept() should be logged, and the user can skip the log in the plugin.
--
portl4t.cn@gmail.com
已使用 Sparrow (http://www.sparrowmailapp.com/?sig)
在 2014年7月12日 星期六，上午12:00，James Peach 写道：
> On Jul 10, 2014, at 11:00 AM, Acácio Centeno <acacio.centeno@azion.com (mailto:acacio.centeno@azion.com)> wrote:
>
> > Hi,
> >
> > I'm writing a plugin that uses the API function TSHttpTxnServerIntercept()
> > to overwrite origin access. However, we've observed that when the plugin
> > does so the request is not logged to the access log.
> >
>
>
> That rings a bel, though I've never investigated it.
>
> > Is that correct? If so, is there a function I could call from the plugin to
> > manually write to the access log?
> >
>
>
> I can see how TSHttpTxnIntercept() would cause most logging to be skipped, but off the top of my head, I would have thought that TSHttpTxnServerIntercept() could be logged. I think that the best approach is to fix this in core. There's no API to construct an internal log record.
>
> > I've seen that I can create a custom log using TSTextLogObjectCreate() /
> > TSTextLogObjectWrite(), but it would be weird to have misses logged to a
> > file and hits to another.
> >
>
>
> Yeh that would suck :-/
>
> >
> > Thanks,
> > Acácio Centeno
> > Software Engineering
> > Azion Technologies
> > Porto Alegre, Brasil +55 51 3012 3005 | +55 51 8118 9947
> > Miami, USA +1 305 704 8816
> >
> > Quaisquer informações contidas neste e-mail e anexos podem ser
> > confidenciais e privilegiadas, protegidas por sigilo legal. Qualquer forma
> > de utilização deste documento depende de autorização do emissor, sujeito as
> > penalidades cabíveis.
> >
> > Any information in this e-mail and attachments may be confidential and
> > privileged, protected by legal confidentiality. The use of this document
> > require authorization by the issuer, subject to penalties.
> >
>
>
>
Re: 回复： Using TSHttpTxnServerIntercept() prevents logging?
Posted by Acácio Centeno <ac...@azion.com>.
How would the plugin skip the log? Maybe I'm doing something that is
leading to the log skipping without being aware of it.
Acácio Centeno
Software Engineering
Azion Technologies
Porto Alegre, Brasil +55 51 3012 3005 | +55 51 8118 9947
Miami, USA +1 305 704 8816
Quaisquer informações contidas neste e-mail e anexos podem ser
confidenciais e privilegiadas, protegidas por sigilo legal. Qualquer forma
de utilização deste documento depende de autorização do emissor, sujeito as
penalidades cabíveis.
Any information in this e-mail and attachments may be confidential and
privileged, protected by legal confidentiality. The use of this document
require authorization by the issuer, subject to penalties.
On Sat, Jul 12, 2014 at 12:39 AM, <po...@gmail.com> wrote:
> I did not have this problem as our trafficserver is based on 3.2, I don’t
> know whether there is something changed.
> I think both TSHttpTxnIntercept() and TSHttpTxnServerIntercept() should be
> logged, and the user can skip the log in the plugin.
>
>
> --
> portl4t.cn@gmail.com
> 已使用 Sparrow (http://www.sparrowmailapp.com/?sig)
>
>
> 在 2014年7月12日 星期六，上午12:00，James Peach 写道：
>
> > On Jul 10, 2014, at 11:00 AM, Acácio Centeno <acacio.centeno@azion.com
> (mailto:acacio.centeno@azion.com)> wrote:
> >
> > > Hi,
> > >
> > > I'm writing a plugin that uses the API function
> TSHttpTxnServerIntercept()
> > > to overwrite origin access. However, we've observed that when the
> plugin
> > > does so the request is not logged to the access log.
> > >
> >
> >
> > That rings a bel, though I've never investigated it.
> >
> > > Is that correct? If so, is there a function I could call from the
> plugin to
> > > manually write to the access log?
> > >
> >
> >
> > I can see how TSHttpTxnIntercept() would cause most logging to be
> skipped, but off the top of my head, I would have thought that
> TSHttpTxnServerIntercept() could be logged. I think that the best approach
> is to fix this in core. There's no API to construct an internal log record.
> >
> > > I've seen that I can create a custom log using TSTextLogObjectCreate()
> /
> > > TSTextLogObjectWrite(), but it would be weird to have misses logged to
> a
> > > file and hits to another.
> > >
> >
> >
> > Yeh that would suck :-/
> >
> > >
> > > Thanks,
> > > Acácio Centeno
> > > Software Engineering
> > > Azion Technologies
> > > Porto Alegre, Brasil +55 51 3012 3005 | +55 51 8118 9947
> > > Miami, USA +1 305 704 8816
> > >
> > > Quaisquer informações contidas neste e-mail e anexos podem ser
> > > confidenciais e privilegiadas, protegidas por sigilo legal. Qualquer
> forma
> > > de utilização deste documento depende de autorização do emissor,
> sujeito as
> > > penalidades cabíveis.
> > >
> > > Any information in this e-mail and attachments may be confidential and
> > > privileged, protected by legal confidentiality. The use of this
> document
> > > require authorization by the issuer, subject to penalties.
> > >
> >
> >
> >
>
>
>