Oh man, I ran into the same issue last week! The whole localhost thing feels like a weird hack, but yeah, that’s just how curl how to specify path when using a socket works.
If you’re tired of guessing, check out httpie—it’s a bit more intuitive for unix sockets.
Command looks like:
`http --unix-socket /tmp/socket.sock localhost/path`
Way cleaner, imo.
If you’re tired of guessing, check out httpie—it’s a bit more intuitive for unix sockets.
Command looks like:
`http --unix-socket /tmp/socket.sock localhost/path`
Way cleaner, imo.
