NE_GET_REQUEST_TARGE(3)

📦
version 0.37.1 · 7 versions
, in arch rolling

💅 NE_GET_REQUEST_TARGE(3) 💅

ok so this is a page from the neon API reference, and honestly? it's a lil one but it's important, bestie. stay with me.

✨ NAME ✨

ne_get_request_target — retrieve request target 🎯

🦋 SYNOPSIS 🦋

#include <ne_request.h>

const ne_uri *ne_get_request_target(ne_request *req);

like, that's it. that's the whole vibe. one function, one pointer, no drama. 🫶

🌸 DESCRIPTION 🌸

okay so ne_get_request_target returns the request target URI, and it hands it back to you as a pointer to an ne_uri object. cute, right? 💖

now the "target resource" of a request — that's a real official concept, defined per Section 7.1 of RFC 9110[1], no cap. and the way it gets derived is: it comes from the parameters you used to create the request with ne_request_create(3), plus the parameters you used to create the session with ne_session_create(3). so like, both of those things feed into it. it's giving collaborative. ✨

🎀 RETURN VALUE 🎀

the function returns an ne_uri, or NULL if it wasn't possible to create the target URI. 😭 and lowkey, that NULL case can only happen if the path you used to create the request object was not a valid URI path. so like, if you see a NULL, check your path, bestie.

⚠️ also heads up: the path field of the returned object can be the empty string if the authority-form of the URI is used. that's not a bug, that's just how it is. don't come for me. 💅

🌈 HISTORY 🌈

ne_get_request_target is available in neon 0.34.0 and later. so if you're on something ancient, that's a you problem, upgrade era. 👑

🦋 SEE ALSO 🦋

go read those too, iykyk. 📚

Copyright © 2001-2026 Joe Orton

⭐ REFERENCES ⭐

  1. Section 7.1 of RFC 9110 https://www.rfc-editor.org/rfc/rfc9110.html#section-7.1

and that's the whole page, bestie!! 🎀 this lil slice of the neon manual is from the 03/20/2026 drop, and it's literally iconic. slay, bye! 💅✨

📦 where this page comes from