TSNETACCEP...EDPROTOCOL(3ts)

📦
version 9.2.5 · 4 versions
, in ubuntu noble, ubuntu questing

💖 TSNetAcceptNamedProtocol(3ts) 💖

okay bestie, sit down, hydrate, and let me tell you about TSNetAcceptNamedProtocol from the Apache Traffic Server 3ts manual. this one is giving ✨TLS protocol registration✨ and honestly? iconic.

✨ NAME ✨

TSNetAcceptNamedProtocol — listen on all SSL ports for connections for the specified protocol name 🎀

✨ SYNOPSIS ✨

#include <ts/ts.h>

TSReturnCode TSNetAcceptNamedProtocol(TSCont contp, const char *protocol)

like yes, two args, that's it, she's lowkey simple 🦋

✨ DESCRIPTION ✨

so TSNetAcceptNamedProtocol registers the specified protocol for all statically configured TLS ports. no cap.

when a client rolls up using the TLS Next Protocol Negotiation extension and negotiates the protocol you asked for, Traffic Server will route the request straight to the given handler contp. main character routing fr fr 👑

NOTE: be aware that the protocol is not registered on ports opened by other plugins. so like, if another plugin opened a port, that's their house, not yours 💅

the event and data handed to the handler are the same as for TSNetAccept(). if a connection is successfully accepted, the event code will be TS_EVENT_NET_ACCEPT and the event data will be a valid TSVConn bound to the accepted connection. slay 🌸

IMPORTANT: neither contp nor protocol are copied. they must remain valid for the lifetime of the plugin. so don't go freeing your strings early bestie, that's how you get undefined chaos 😭

TSNetAcceptNamedProtocol fails if the requested protocol cannot be registered on all of the configured TLS ports. if it fails, the protocol will not be registered on any ports. there is no partial failure. it's all or nothing, periodt 💀

2026, dev@trafficserver.apache.org

and that's the whole vibe check 🫶 this was the 9.2 release, dated Feb 12, 2026, page TSNETACCEP...EDPROTOCOL(3ts). go forth and register your protocols, bestie, iykyk ✨💖🎀

📦 where this page comes from