-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Review support of AF_UNIX sockets on the Windows port #9571
Comments
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions. |
@snowp this remains a placeholder, could you add help wanted (or we can leave it closed for the time being) |
Note that this is experimentally introduced in #10293 although has yet to be thoroughly reviewed and tested. |
It appears we've made enough progress to consider this placeholder completed. |
Windows introduced AF_UNIX domain socket support to the winsock API with the Insider Build 17063 which dropped in Dec '17. This should now be available mainstream on most deployed Server 2019, although this needs to be validated.
https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
In porting this support, Envoy should gracefully degrade where the afunix.sys driver is not installed.
The text was updated successfully, but these errors were encountered: