KHTML_PUTS(3)

💅 KHTML_PUTS(3) — like, the kcgihtml string-putting era ✨

okay bestie, so this is a page from the Library Functions Manual and it's about khtml_puts — literally the moment your C code gets to say words out loud on a web page 🫶

---

🌸 NAME 🌸

khtml_puts — put string content for kcgihtml. that's it, that's the whole vibe 🎀

📚 LIBRARY 📚

library “libkcgihtml” — yes queen, that's the one 💖

✨ SYNOPSIS ✨

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

enum kcgi_err
khtml_puts(struct khtmlreq *req, const char *cp);

🦋 DESCRIPTION 🦋

So basically it writes a NUL-terminated string cp into a context req — and req has to be one you already initialised with khtml_open(3), no shortcuts bestie 😌

Here's the cute part: if cp is NULL, it literally does nothing and returns success. iconic. no drama, no crash, just vibes 💅

All of the content gets HTML escaped — so for example, the left-angle bracket "<" gets rendered as "<". ngl that's the whole point, you can't have your user string breaking out and becoming markup, that would be a main character moment of the bad kind 💀

And heads up: it does not append a newline like puts(3) does. no cap, different function, different rules ⭐

🔥 RETURN VALUES 🔥

Returns an enum kcgi_err telling you the error state. here's the whole lineup:

• KCGI_OK — success!! not an error, we're thriving 🌈
• KCGI_ENOMEM — internal memory allocation failure 😭 the allocator said no
• KCGI_HUP — the output connection has been terminated. for FastCGI connections, you should release the current connection with khttp_free(3) and reenter the parse loop 🫶
• KCGI_FORM — the connection is still expecting headers with khttp_head(3). this indicates that khttp_body(3) did not return with success or was not invoked. for FastCGI connections, you should release the current connection with khttp_free(3) and reenter the parse loop 🙈
• KCGI_SYSTEM — internal system error writing to the output stream 💀

lowkey memorise those last two, they both tell you to khttp_free(3) and reenter the parse loop. fr fr, same instructions, different causes.

🎀 EXAMPLES 🎀

The following outputs a simple HTML page. it assumes r is a struct kreq pointer. for brevity, it does not do any error checking (do as the manpage says, not as the manpage does, bestie 😭):

khttp_head(r, kresps[KRESP_STATUS],
  "%s", khttps[KHTTP_200]);
khttp_head(r, kresps[KRESP_CONTENT_TYPE],
  "%s", kmimetypes[KMIME_TEXT_HTML]);
khttp_body(r);
khtml_open(&req, r, 0);
khtml_elem(&req, KELEM_DOCTYPE);
khtml_elem(&req, KELEM_HTML);
khtml_elem(&req, KELEM_BODY);
khtml_elem(&req, KELEM_P);
khtml_puts(&req, "Hello, world.");
khtml_close(&req);

look at that. "Hello, world." — the original hello world, the blueprint, the moment 💖✨

👀 SEE ALSO 👀

• kcgihtml(3)

📏 STANDARDS 📏

The referenced HTML5 standard is HTML5.2: https://www.w3.org/TR/html52.

👑 AUTHORS 👑

Written by Kristaps Dzonsons <kristaps@bsd.lv>. we stan a legend 🫶

---

🧚 cute little sign-off 🧚

this page came from Debian, its version stamp is $Mdocdate$, and it's filed under KHTML_PUTS(3). periodt. now go escape some strings, bestie 💜🌸