-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add support for unix socket as upstream #1866
Add support for unix socket as upstream #1866
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.
Would like to see some tests, similar to the HTTP tests, but we will need to work out how to create a temporary unix socket. I wonder if the HTTP test server supports this already? 🤔
How is currently started the upstream http to test against ? |
We create an http testserver in the suite setup, perhaps we can create something there that sets up a unix socket? Otherwise code LGTM Apologies for the delay in getting back to you |
I remember myself doing the server portion, but can't put my hand on it... |
This pull request has been inactive for 60 days. If the pull request is still relevant please comment to re-activate the pull request. If no action is taken within 7 days, the pull request will be marked closed. |
still alive |
Unix mock is available at |
This pull request has been inactive for 60 days. If the pull request is still relevant please comment to re-activate the pull request. If no action is taken within 7 days, the pull request will be marked closed. |
I miss the reminder of the bot. |
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.
Tests wise, lets make sure there's something added to the proxy tests.
You'll need to add a new unix based upstream to the upstreams and then add one or more Entry blocks that exercises that new endpoint
This pull request has been inactive for 60 days. If the pull request is still relevant please comment to re-activate the pull request. If no action is taken within 7 days, the pull request will be marked closed. |
Review needed still relevant |
This pull request has been inactive for 60 days. If the pull request is still relevant please comment to re-activate the pull request. If no action is taken within 7 days, the pull request will be marked closed. |
damn, I missed the reminder @JoelSpeed :/ |
Knowing that test have been added, is there anything else to do to see this PR merged ? |
@babs I'll try to find some time to test it on the weekend :) |
a721672
to
06a8424
Compare
@tuunit @JoelSpeed rebased, changelog updated ;) |
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 @babs
Description
Add support for unix socket at upstream
Might require some rework.
Should be able to close #1865
Motivation and Context
Some apps might require to go through a unix socket when listening on a tcp port, even bound locally is not secure enough and socket ownership is used as an extra isolation layer.
How Has This Been Tested?
I created a simple uvicorn app that listen to unix socket and used
--upstream=unix:///path/pf/the/unix.sock
.Checklist: