It may be simpler but it is still not completely determined.
On Wed, Jul 8, 2020 at 10:28 AM Sudheer Vinukonda
wrote:
> Right, I understand that. But, the server side protocol stack isn’t as
> varied or has anywhere as many combinations as the client side and is
> largely determined by system wi
Is there another way for Traffic Dump to know what the protocol stack is on
the server side on a per transaction basis? Without this server-side API,
it seems it would not be easy for Traffic Dump or any plugin to get this
information. It is being added to satisfy a need Traffic Dump has. As you
po
Right, I understand that. But, the server side protocol stack isn’t as varied
or has anywhere as many combinations as the client side and is largely
determined by system wide setting on the ATS side, no? I suppose it may add
some sort of symmetry, but I wonder if it somehow feels superfluous.
The TSHttpTxnServerProtocolStackGet and
TSHttpTxnServerProtocolStackContains are read only. They do not customize
the Server protocol stack, but they give the plugin the ability to analyze
the Server protocol stack. Since there can be variances (TLS, client
certificate requirements), it seems lik
>> 1. Add TSHttpTxnServerProtocolStackGet and
>>TSHttpTxnServerProtocolStackContains. These are the server-side
analogues to the already existing client-side functions.
Hmm...not sure if we should be adding these API - AFAIK, we still don't really
support customizing the Server protocol
