ucspi-proxy-http-xlate(1)

💖 ucspi-proxy-http-xlate 💖

okay bestie, gather round, because this one is so cool and also like, exactly what it says on the tin. it lives in the General Commands Manual section, and it's a little translating proxy and it's lowkey iconic. 🎀

✨ NAME ✨

ucspi-proxy-http-xlate — a translating HTTP proxy. yes queen, it does find-and-replace on the fly. 💅

🌸 SYNOPSIS 🌸

ucspi-proxy-http-xlate [ -v ] search replace [ search replace [...]]

🦋 DESCRIPTION 🦋

so here's the vibe: ucspi-proxy-http-xlate is a HTTP proxy for a UCSPI client/server pair, and it can translate strings within HTTP content on the fly, like literally while it's flowing through. ✨

every single occurrence of search gets replaced with replace. every one. no cap. 🫶

and here's the detail that's giving main character energy: if the HTTP response from the server contained a Content-Length header, it gets replaced with the length of the translated content. because girl, the numbers changed, we gotta say so. 😌

you can pass as many search replace pairs as your heart desires — [ search replace [...] ] — and each pair does its thing. 🔥

👑 SEE ALSO 👑

• ucspi-proxy(1) — the og. go say hi. 💜

💀 CAVEATS 💀

okay so, real talk, bestie, listen to me on this one: all content is translated. like, all of it. no filtering, no vibe check, nothing.

that means if a search string happens to show up inside a binary response — think an image, for example — you can get some odd side-effects. it's not malicious, it's just that this thing does not know or care what it's rewriting. so pick your search strings like you mean it. 🙈

anyway, that's the whole page!! mwah. 😭💖

this was ucspi-proxy-http-xlate(1) from the General Commands Manual — and yeah, the footer is just the page name again, ucspi-proxy-http-xlate(1), because the manpage said its own name one last time on the way out. cute. slay. bye bestie!! 🌈⭐🎀