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
Should connect-tcp return the ip and port that get assigned to the client in the response header, like we did in connect-udp-listen?
The text was updated successfully, but these errors were encountered:
The TCP client address is almost never of any interest, since it cannot be reused for other connections. Do you have a use case for this metadata?
Sorry, something went wrong.
@asingh-g I would expect that this could be a useful extension for a specific use case, rather than something in the base spec?
Agree sounds like an extension
No branches or pull requests
Should connect-tcp return the ip and port that get assigned to the client in the response header, like we did in connect-udp-listen?
The text was updated successfully, but these errors were encountered: