-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Support unix domain sockets in the http client [MERGED] #322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @seanyoung
I like the changes in general, but they should be split into smaller patches (I count 3, evhttp_uri, server accepting changes, client making request changes)
Are you still interesting in this? If so, can you please split them?
P.S. and I'm very sorry for not paying attention before.
There are no standard for encoding a unix socket in an url. nginx uses: http://unix:/path/to/unix/socket:/httppath The second colon is needed to delimit where the unix path ends and where the rest of the url continues. Signed-off-by: Sean Young <sean@mess.org>
Please let me know if you want to split the commit when you come round to reviewing it in 2025. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
I've addressed my comments, but I can't push to your topic branch, will apply the patch to upstream w/o updating PR then, and close PR after (so it will not have merged icon).
Applied. Upstream commit is f446229. |
There are no standard for encoding a unix socket in an url. nginx uses:
http://unix:/path/to/unix/socket:/httppath
The second colon is needed to delimit where the unix path ends and where
the rest of the url continues.