KHTTP_PUTC(3)

💖 KHTTP_PUTC(3) — put character content for kcgi 💖

Hiii bestie, welcome to KHTTP_PUTC(3) from the Library Functions Manual — this is the little character-pusher for kcgi, and yes, she ate. 🎀

---

🌸 LIBRARY 🌸

library “libkcgi” — that's the one, no cap. 🦋

---

✨ SYNOPSIS ✨

#include <sys/types.h>
#include <stdarg.h>
#include <stdint.h>
#include <kcgi.h>

enum kcgi_err
khttp_putc(struct kreq *req, int c);

---

💅 DESCRIPTION 💅

Okay so khttp_putc writes a character c — converted to an unsigned char, bestie, don't forget that glow-up — into a kcgi(3) context req that was allocated with khttp_parse(3) or khttp_fcgi_parse(3). 🫶

Call it only after khttp_body(3), okay? That's the vibe check. ✨

⚠️ Bestie warning: if kcgi_writer_disable(3) has been previously invoked, this function will abort(3). Not cute, not slay — just facts. 💀

---

🔥 RETURN VALUES 🔥

It returns an enum kcgi_err indicating the error state. Here's the whole squad:

• KCGI_OK — Success. Not an error, just main character energy. 👑
• KCGI_ENOMEM — Internal memory allocation failure. The memory said "not today." 😭
• KCGI_HUP — The output connection has been terminated. For FastCGI connections, the current connection should be released with khttp_free(3) and the parse loop reentered. 🦋
• KCGI_FORM — The connection is still expecting headers with khttp_head(3). Indicates that khttp_body(3) did not return with success or was not invoked. For FastCGI connections, the current connection should be released with khttp_free(3) and the parse loop reentered. 🙈
• KCGI_SYSTEM — Internal system error writing to the output stream. System said "error" and meant it. 💀

---

🌈 SEE ALSO 🌈

• kcgi(3)
• kcgi_writer_disable(3)
• khttp_body(3)
• khttp_parse(3)

iykyk — go read those too, bestie. 💜

---

🎀 AUTHORS 🎀

Written by Kristaps Dzonsons <kristaps@bsd.lv>. Iconic behavior, periodt. ⭐

---

kisses and sparkles, this page is KHTTP_PUTC(3), coming at you from Debian and stamped with $Mdocdate$ — bye bestie, slay your output 💅💖