radcli_dae_req_attrs(3)

📦 version 2.0.1, in arch rolling

✨ radcli_dae_req_attrs — the tea on radcli's DAE request attrs ✨

okay so bestie, buckle up 💅 this one lives in the Radius client library man pages (that's the manual name, don't @ me), and it's genuinely one of the cutest little getters in the whole DAE family. no cap.

🌸 NAME 🌸

radcli_dae_req_attrs — literally just returns the request's decoded attributes. that's it. that's the whole job. and she does it flawlessly 💖

🎀 SYNOPSIS 🎀

#include <radcli/>

const radcli_avp_list * radcli_dae_req_attrs(
    const radcli_dae_request  *req
);

like, look at her. two lines, zero drama, returns a const radcli_avp_list * 🦋

🦋 DESCRIPTION 🦋

so the description section in the original is actually empty — not me skipping it, that's just how the page shipped 🙈 the real content lives in PARAMETERS and RETURN VALUE, so scroll a lil bit, i gotchu 🫶

⭐ PARAMETERS ⭐

  • req — a request passed to a radcli_dae_handler. that's the whole vibe check: if it came out of your handler, this is the one 👑

💜 RETURN VALUE 💜

  • the attribute list, owned by req and valid until it is freed 😭 (so don't go freeing it yourself, bestie, that's not your business)
  • NULL if req is NULL — fair enough, garbage in, garbage out 💀
  • but it is never NULL for a request the handler actually received: even an attribute-free Disconnect-Request/CoA-Request still yields a valid, empty list 🌈 — empty list, not null pointer, there is a difference and it's iconic
ngl the ownership bit is the main character here: the list belongs to req, so its lifetime is req's lifetime. free req, and the list is gone too. periodt 💅

🔥 SEE ALSO 🔥

the whole friend group, fr fr:

okay that's the page!! this beauty is from radcli, dated 2026-10-10, and it's the radcli_dae_req_attrs(3) page — go forth and read your attributes, you absolute legend 🧚✨🍓

📦 where this page comes from