KHTTP_EPOCH2STR(3)

okay bestie, welcome to the KHTTP_EPOCH2STR(3) page — it lives in the Library Functions Manual, and it's literally about turning epoch time into a string. 🕰️✨

🎀 NAME 🎀

khttp_epoch2str, khttp_epoch2ustr — convert time to a string 💖

📚 LIBRARY 📚

library “libkcgi” — yes, that's the one, bestie.

✨ SYNOPSIS ✨

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

char *
khttp_epoch2str(int64_t epoch, char *buf, size_t sz);

char *
khttp_epoch2ustr(int64_t epoch, char *buf, size_t sz);

🦋 DESCRIPTION 🦋

okay so here's the vibe: these functions format an epoch value (seconds since Jan 1, 1970, 00:00:00 UTC) into the buffer buf of size sz, and sz should be greater than or equal to 64 bytes. 💅 If there isn't enough space for the formatted date, the buffer is truncated to the available size. It is always NUL-terminated — always, no cap. 🫶

The output of khttp_epoch2str() conforms to RFC 5322 (“Wed, 02 Oct 2002 13:00:00 GMT”). 🗓️ But heads up: the year may be greater than four digits or less than 1900, or even be negative — which is contrary to RFC 5322 section 3.3. Not me causing chaos, it's just in the docs. 😭

khttp_epoch2ustr() conforms to ISO 8601 (“2002-10-02T13:00:00Z”), again with the stipulation that the year may be greater than 4 digits or be less than zero. 🌈

These deprecate the original kutil_epoch2str() and kutil_epoch2utcstr() functions, which had undefined behaviour in some corner cases. 💀 So yeah, use the new ones, bestie.

💜 RETURN VALUES 💜

Returns a pointer to the input buf or NULL if buf is NULL, sz is zero, or time conversion fails. That's the whole check, periodt. 👑

🧚 SEE ALSO 🧚

• khttp_datetime2epoch(3)
• khttp_epoch2datetime(3)
• khttp_epoch2tms(3)

🌟 AUTHORS 🌟

Written by Kristaps Dzonsons <kristaps@bsd.lv>. 👑 Iconic behaviour, honestly.

---

cute sign-off: this page came from Debian, with the $Mdocdate$ date stamp, and it's the KHTTP_EPOCH2STR(3) page. mwah 💋✨