-
Notifications
You must be signed in to change notification settings - Fork 5
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
Secure tunnel v3 #84
Secure tunnel v3 #84
Conversation
* Back compat for V3 with V1 and V2 and tests --------- Co-authored-by: Michael Graeb <graebm@amazon.com>
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.
Looks good to me!
There was only one super trivial nitpick but it can be skipped if you want, as it's just a super minor comment change.
@@ -67,7 +67,7 @@ enum aws_secure_tunnel_message_type { | |||
|
|||
/** | |||
* ConnectionReset messages convey that the connection has ended, either in error, or closed intentionally for the | |||
* tunnel peer. | |||
* tunnel peer. These should not be manually sent from either Destination or Source clients. |
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.
Nitpick: If this is for testing only, which I think was mentioned in the struct/enum for reset, I'd add a note about it here too. Something like "This is only used for testing internally" or something, so the customer knows that they should never expect to see this in a real world application.
* added jitter for reconnecting * remove some logging from websocket request headers
* added ability to pass in tls options * dns ping reduction * builder v0.9.38
* added ability to pass in tls options * dns ping reduction * builder v0.9.38
Adding Connection IDs to Secure Tunnel
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.