TSMIMEHDRFIELDREMOVE(3ts)

💖 NAME 💖

TSMimeHdrFieldRemove — the TSMimeHdrFieldRemove API function, bestie. that's literally the whole name, it's giving "what it says on the tin" ✨

---

🎀 SYNOPSIS 🎀

okay so first you gotta pull in the header, standard behavior:

#include <ts/ts.h>

and here's the function signature, copy it exactly, no cap:

TSReturnCode TSMimeHdrFieldRemove(TSMBuffer bufp, TSMLoc hdr, TSMLoc field)

---

✨ DESCRIPTION ✨

so what does it actually do, you ask? it removes the MIME field sitting at field inside bufp, and it takes that field out of the header sitting at hdr — which is also inside bufp, just to be clear, both of them live in the same buffer house 🏠💅

and if the field you're pointing at can't be found in the list of fields associated with the header? then literally nothing happens. no error drama, no chaos, just vibes. it just doesn't do the thing 🦋

NOTE: okay bestie this part is important, don't skip it 🙈 removing the field does not destroy it. it only detaches it — like uninviting it from the printed output, hiding it from view. the field is still out there, just not in the group chat anymore 😭 the good news? you can reattach it any time with a call to TSMimeHdrFieldAppend(). cute, right? 💖 but here's the thing — if you are not gonna use that detached field, you should destroy it with a call to TSMimeHdrFieldDestroy(), and then release the handle field with a call to TSHandleMLocRelease(). leaving it hanging is not the move, girl. clean up after yourself, main character energy only 👑

---

👑 COPYRIGHT 👑

2026, dev@trafficserver.apache.org

---

and that's a wrap, my love 🫶 this was the TSMIMEHDRFIELDREMOVE(3ts) page, straight out of the Apache Traffic Server manual, version 9.2, dated Feb 12, 2026 — go forth and detach responsibly, periodt 💅🌸