Fun fact: This isn’t just a curl thing. Other tools like wget have similar quirks with unix sockets.
For curl how to specify path when using a socket, the hostname is basically ignored, but the field must exist. Dumb, but consistent?
If you’re on macOS, double-check socket paths—they’re case-sensitive there for some reason.
For curl how to specify path when using a socket, the hostname is basically ignored, but the field must exist. Dumb, but consistent?
If you’re on macOS, double-check socket paths—they’re case-sensitive there for some reason.
