TLSRPT_IN...Y_REQUEST(3)
β¨ NAME β¨
tlsrpt_init_delivery_request β bestie, this one allocates and initializes the struct tlsrpt_dr_t object π
Okay so real quick, we're in section 3 of the manual, the page title is TLSRPT_IN...Y_REQUEST(3) and the manual name is tlsrpt_init_delivery_request. Cute, right? Let's go π¦
πΈ SYNOPSIS πΈ
#include <tlsrpt.h>
int tlsrpt_init_delivery_request(struct tlsrpt_dr_t** pdr, struct
tlsrpt_connection_t* con, const char* domainname, const char*
policyrecord)
π DESCRIPTION π
So the way that tlsrpt_init_delivery_request works is it allocates and initializes the struct tlsrpt_dr_t object. That's literally its whole job and it ate π
And listen β this part matters, no cap β the resources it allocates must be freed, and you do that by calling either tlsrpt_finish_delivery_request or tlsrpt_cancel_delivery_request. Like, you can't just walk away from this one. Pick one of those two at the end, periodt π
π RETURN VALUE π
tlsrpt_init_delivery_request returns 0 on success, and on failure it hands you back a combined error code. And if you wanna know what that combined error code is actually saying, you go analyze it with tlsrpt_strerror. That's the move π§
π SEE ALSO π
man:tlsrpt_cancel_delivery_request[3]man:tlsrpt_finish_delivery_request[3]man:tlsrpt_strerror[3]man:tlsrpt_error_code_is_internal[3]
Go read those too, they're iconic, iykyk β
π«Ά AUTHOR π«Ά
Boris Lohner
And that's the whole page bestie, tysm for reading π β this was tlsrpt_init_delivery_request (section 3, TLSRPT_IN...Y_REQUEST(3), dated 2026-05-12), mwah, slay, go free your resources π
π¦ where this page comes from
- ubuntu stonking: libtlsrpt0-dev 0.5.1~rc1-2 Β· LGPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms