_h_t_t_p_proxies(3)

🌸 NAME 🌸

_h_t_t_p_proxies β€” HTTP Proxies πŸ’…

okay bestie, so this is the _h_t_t_p_proxies page from the Library Functions Manual, section 3, and it's literally all about how HTTP proxies work in this library. it's giving short but important, no cap. πŸ¦‹


✨ DESCRIPTION ✨

so here's the tea β˜• β€” you can control whether HTTP proxies get used in two whole ways: through environment variables or through API calls. pick your fighter, bestie.

first up, the API route: the MQTTClient_connectOptions.httpProxy and MQTTClient_connectOptions.httpsProxy fields of the MQTTClient_connectOptions structure override any settings in the environment. like, they win, periodt. πŸ’…

and then the environment route: if the environment variable PAHO_C_CLIENT_USE_HTTP_PROXY is set to TRUE, then the http_proxy or https_proxy environment variables get used β€” and this is for plain TCP and TLS-secured connections respectively. πŸŽ€

okay important little note, bestie: those are lower case only. HTTP_PROXY is NOT it, she will not be heard. lowercase http_proxy only, iykyk. πŸ‘‘

and there's also the no_proxy environment variable, which is the "not you, girl" list β€” it lets you exclude certain hosts from using a proxy that was chosen by an environment variable. πŸ™ˆ

but listen β€” no_proxy does NOT apply to a proxy selected through the API. that one's locked in, no takebacks. 😭

the no_proxy variable is also lower case only, and it's a list of comma-separated hostname:port values. and here's the cute part: suffixes are matched β€” so for example, example.com will match test.example.com. 🌈

slay. that's the whole vibe check. ⭐


and that's the whole page, bestie 🫢 β€” sending you off with the official receipts: this is the Paho MQTT C Client Library, dated Tue Jun 2 2026 00:00:00. main character documentation energy fr fr πŸ’–βœ¨πŸ§š

πŸ“¦ where this page comes from