I created a PR for this.
https://github.com/apache/trafficserver/pull/12032
Having ProxyProtocol in the name would be a bit confusing. One could read
it like VConnProxy and ProtocolInfo.
PROXY is an option, but not my preference.
I kept PP on the PR.
-- Masakazu
On Sun, Feb 9, 2025 at 11:19 AM
That’s another idea. I suppose between PROXY and PP I’d stick with PP.
Brian
"Come to Me, all who are weary and heavy-laden, and I will
give you rest. Take My yoke upon you and learn from Me, for
I am gentle and humble in heart, and you will find rest for
your souls. For My yoke is easy and My bu
I’m +1 too.
Adding ProxyProtocol seems pretty long, maybe we can use PROXY (all upper
case) instead of PP, which is how it’s spelled.
— Leif
On Sat, Feb 8, 2025 at 20:03 Brian Neradt wrote:
> +1
>
> My preference would be to spell out ProxyProtocol in the API instead of
> PP. But I don't feel
+1
My preference would be to spell out ProxyProtocol in the API instead of PP.
But I don't feel that strongly about it though. +1 either way.
On Fri, Feb 7, 2025 at 7:21 PM Masakazu Kitajo wrote:
> Hi,
>
> I'd like to propose a new TS API to access information from PROXY protocol.
>
> ATS suppo
Hi,
I'd like to propose a new TS API to access information from PROXY protocol.
ATS supports PROXY protocol, which carries connection information between a
client and a LB (basically the 5-tuple). And I recently added the support
for PROXY protocol version 2 TLV (Type-Length-Value) fields, which
