We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Binding to port 0 is more reliable in any cases. Also, current implementation keeps open socket at port 1100.
But support of binding to port 0 requires API methods to retrieve port to which server was bound.
Linked CoreLibs issue: AdguardTeam/CoreLibs#1028
The text was updated successfully, but these errors were encountered:
Done.
Testing instructions for QA:
Sorry, something went wrong.
admitrevskiy
No branches or pull requests
Binding to port 0 is more reliable in any cases. Also, current implementation keeps open socket at port 1100.
But support of binding to port 0 requires API methods to retrieve port to which server was bound.
Linked CoreLibs issue:
AdguardTeam/CoreLibs#1028
The text was updated successfully, but these errors were encountered: