trafficserver-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Peach <>
Subject Re: TS-4703 && PR-829
Date Fri, 29 Jul 2016 00:28:59 GMT

> On Jul 29, 2016, at 12:29 AM, Susan Hinrichs <>
> On 7/28/2016 5:05 AM, James Peach wrote:
>>> On Jul 28, 2016, at 7:33 PM, James Peach <> wrote:
>>>> On Jul 28, 2016, at 5:50 AM, Petar Bozhidarov Penkov <>
>>>> Hello,
>>>> I am writing in accordance with the referenced Pull Request and JIRA issue.
>>>> I am proposing a GET-er method for Transactions's underlying protocol. This
>>>> relates to TS-2987 and is effectively one of the proposed solutions, a
>>>> wrapper around ProxyClientTransaction::get_protocol_string() . The proposed
>>>> API is as follows:
>>>> *tsapi const char *TSHttpTxnClientProtocolGet(TSHttpTxn txnp);*
>>>> **name credit goes to Susan Hinrichs and Alan Carroll*
>>> Hi Petar,
>>> I’m not sure that this is the right approach. get_protocol_string() simply
distinguishes HTTP/2 sessions, so it it not something that I think is ready to become API.
Since we already have an abstraction for HTTP versions (see TSHttpHdrVersionGet), maybe a
better approach is to expose a convenience API that returns the transaction HTTP version as
a TS_HTTP_VERSION() constant.
>> We also have a pending review for TSHttpTxnIsWebsocket(), which seems to overlap
with this proposal.
> Yes, we would like to know whether the transaction is part of a Http/1.x session or a
Http/2 session (or whatever else comes up in the future.

Do you have a concrete use case for knowing this?

View raw message