NNG_TLS_CONFIG_SERVER_NAME(3tls)

🎀 NAME 🎀

nng_tls_config_server_name — bestie, this is the one that sets the remote server name 💖

It lives in the NNG Reference Manual, section 3tls, and yeah it's a manual page, but like... a fun one? Okay let's go ✨

---

🌸 SYNOPSIS 🌸

#include <nng/nng.h>
#include <nng/supplemental/tls/tls.h>

int nng_tls_config_server_name(nng_tls_config *cfg, const char *name);

---

✨ DESCRIPTION ✨

okay so here's the tea ☕ — nng_tls_config_server_name() configures the remote server name that a client is gonna use when it connects to a server. Like, this is the name the client walks up to the server wearing 🫶

And what does it actually do with that name? Two things, no cap:

• that name you supply gets used when comparing the identity in the server's certificate 👑 (so it's the thing your cert has to match up to)
• and furthermore, when Server Name Indication (SNI) is in play, that name may be sent over to the server as a hint — a little "hey bestie, use this one please" 🎀 — telling it which of several possible certificates should be used

💅 Tip: this function is only useful in configuring client behavior. Server-side? Not your moment, babe.

---

🌈 RETURN VALUES 🌈

Slays when it works: returns 0 on success, and non-zero otherwise. That's it, that's the vibe check 💖

---

💀 ERRORS 💀

• NNG_ENOMEM — insufficient memory is available 😭 like the system literally cannot right now
• NNG_EBUSY — the configuration cfg is already in use, and cannot be modified 🙈 she's busy, she's booked, she's not taking edits rn

---

🦋 SEE ALSO 🦋

• nng_strerror(3)
• nng_tls_config_alloc(3tls)
• nng_tls_config_auth_mode(3tls)
• nng(7)

---

and that's the whole page!! ✨ this came out of the NNG Reference Manual, dated 2026-06-30 📅 — with love from the NNG girlies, mwah 🫶💖🎀