NE_SET_REQUEST_FLAG(3)

📦
version 0.37.1 · 12 versions
, in arch rolling

💅 NE_SET_REQUEST_FLAG(3) — neon API reference, bestie edition ✨

okay so this is a page from the neon API reference and honestly it's lowkey the plug for tweaking how a single request behaves 🎀

✨ NAME ✨

ne_set_request_flag, ne_get_request_flag — the duo that sets and retrieves per-request flags 🦋

🌸 SYNOPSIS 🌸

#include <ne_request.h>

void ne_set_request_flag(ne_request *req, ne_request_flag flag,
                         int value);

int ne_get_request_flag(ne_request *req, ne_request_flag flag);

💖 DESCRIPTION 💖

So ne_set_request_flag is the one that enables or disables a per-request flag, iykyk. You pass a non-zero value and the flag is on, you pass zero and it's off. That's it, that's the whole vibe check 🫶

Here are the flags that are defined, bestie:

  • NE_REQFLAG_EXPECT100 (default off) — turn this on and you get the "Expect: 100-continue" feature of HTTP/1.1, which lets the server process the request headers without reading the entire request body. It literally saves time and bandwidth if the server throws an authentication challenge (which means the request has to be resent), but ngl it has interoperability problems with some older servers 😭 so like, know what you're doing.
  • NE_REQFLAG_IDEMPOTENT (default on) — disable this one if your request uses a non-idempotent method such as POST. periodt.
  • NE_REQFLAG_1XXTIMEOUT (default on) — disable this flag to disable the overall timeout when reading interim (1xx) responses 👑

⭐ RETURN VALUE ⭐

ne_get_request_flag comes back with zero if the flag is disabled, less than zero if the flag is not supported (rude), or greater than zero if the flag is enabled 💀

🌈 SEE ALSO 🌈

ne_request_create(3).

Copyright © 2001-2026 Joe Orton

okay that's the whole page, go slay 💅✨

— signed off with love from neon, dated 03/20/2026, and yes this was the NE_SET_REQUEST_FLAG(3) page the whole time 🎀🦋🌸

📦 where this page comes from