I think we have to create FetchSM with all the headers from the client request,
should not we?
Is there any other way to get all the headers from the client request?
--
portl4t...@gmail.com
在 2014年8月17日 星期日，上午9:32，James Peach 写道：
> On Aug 16, 2014, at 5:55 PM, portl4t...@gmail.com
> (mailt
I use this api heavily, I think we have to iterate over all headers if we want
to create FetchSM.
I use this api in some plugins, such as Combo, ESI, Slice and so on.
Every time if we want to intercept the HttpSM and create several FetchSM to
construct the real response, this api will be used.
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...@gmail.com
已使用 Sparrow (http://www.sp
