GNURLOPT_UNIX_SOCKET_PATH(3)

💖 GNURLOPT_UNIX_SOCKET_PATH(3): set Unix domain socket 💖

okay bestie, you're on the GNURLOPT_UNIX_SOCKET_PATH(3) page from the curl_easy_setopt options manual, and we are about to make Unix domain sockets make sense. no cap. 💅

🌸 NAME 🌸

CURLOPT_UNIX_SOCKET_PATH — set Unix domain socket.

✨ SYNOPSIS ✨

#include <gnurl/curl.h>

CURLcode curl_easy_setopt(CURL *handle, CURLOPT_UNIX_SOCKET_PATH, char
       *path);

🦋 DESCRIPTION 🦋

So this option turns on Unix domain sockets as the connection endpoint and sets the path to path. If path is NULL, then Unix domain sockets are disabled, periodt. An empty string is not a cute way to disable them — it will result in an error at some point, and it will not disable use of Unix domain sockets. 🙈

When it's enabled, curl will connect to the Unix domain socket instead of establishing a TCP connection to a host. And since no TCP connection is created, curl does not need to resolve the DNS hostname in the URL. slay for less DNS drama. ✨

The maximum path length on Cygwin, Linux and Solaris is 107. On other platforms it might be even less. 💀

Proxy and TCP options such as CURLOPT_TCP_NODELAY(3) are not supported. Proxy options such as CURLOPT_PROXY(3) have no effect either, because these are TCP-oriented, and asking a proxy server to connect to a certain Unix domain socket is not possible.

The application does not have to keep the string around after setting this option. 🫶

🎀 DEFAULT 🎀

Default is NULL, meaning that no Unix domain sockets are used. iconic lazy default, honestly.

🌈 PROTOCOLS 🌈

All protocols except for file:// and FTP are supported in theory. HTTP, IMAP, POP3 and SMTP should in particular work (including their SSL/TLS variants). iykyk. 🔥

🔥 EXAMPLE 🔥

Given that you have an nginx server running, listening on /tmp/nginx.sock, you can request an HTTP resource with:

curl_easy_setopt(curl_handle, CURLOPT_UNIX_SOCKET_PATH, "/tmp/nginx.sock");
curl_easy_setopt(curl_handle, CURLOPT_URL, "http://localhost/");

If you are on Linux and somehow have a need for paths larger than 107 bytes, you could use the proc filesystem to bypass the limitation:

int dirfd = open(long_directory_path_to_socket, O_DIRECTORY | O_RDONLY);
char path[108];
snprintf(path, sizeof(path), "/proc/self/fd/%d/nginx.sock", dirfd);
curl_easy_setopt(curl_handle, CURLOPT_UNIX_SOCKET_PATH, path);
/* Be sure to keep dirfd valid until you discard the handle */

⭐ AVAILABILITY ⭐

Since 7.40.0. 💫

💜 RETURN VALUE 💜

Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not. simple as that, bestie.

🧚 SEE ALSO 🧚

• CURLOPT_OPENSOCKETFUNCTION(3)
• unix(7)

---

ok bye bestie 💖 this has been GNURLOPT_UNIX_SOCKET_PATH(3) from the curl_easy_setopt options manual, libcurl 7.40.0, dated 09 Oct 2014 — go connect to a socket and be iconic ✨🫶