TSHTTPTXNISCACHEABLE(3ts)

💖 TSHTTPTXNISCACHEABLE — the "is this even cacheable bestie" check 💖

okay so this is a page from the 3ts manual, and it's about one very specific little function that answers one very specific little question. let's get into it 🫶

---

✨ NAME ✨

TSHttpTxnIsCacheable — the TSHttpTxnIsCacheable API function. that's it, that's the name, she's straightforward 💅

---

🌸 SYNOPSIS 🌸

#include <ts/ts.h>

TSReturnCode TSHttpTxnIsCacheable(TSHttpTxn txnp, TSMBuffer request,
TSMBuffer response)

look at her. three args, one return code, zero drama ✨

---

🦋 DESCRIPTION 🦋

so the whole vibe here is: you hand this function an upstream response and it tells you whether that response is cacheable given the Traffic Server configuration and state that's live right now. not some hypothetical config, not a config from a dream — the actual current one. 👑

real talk: all of the arguments have to have been grabbed through other API calls before you call this one. no DIY-ing your own buffers, bestie, that's not the move.

the request and response arguments have to point at HTTP header objects. Traffic Server treats them as the request and the response for a transaction respectively — like, that's their whole job in this call. 💖

then it takes the transaction state from txnp, plus whatever is inside request and response, and gives you back:

• TS_SUCCESS — if the response is cacheable 🎉 slay, go off, cache it
• TS_ERROR — otherwise 💀 not today

that's the whole function. short, sweet, does exactly one thing, main character energy fr fr.

---

👑 COPYRIGHT 👑

2026, dev@trafficserver.apache.org

---

and that's the page!! you made it to the end, so proud of you 🥹✨ this was version 9.2 of the TSHTTPTXNISCACHEABLE(3ts) page, dated Feb 12, 2026 — go forth and cache responsibly, bestie 🎀🌈💜