Re-use proxy-client to proxy-server connections, and use HTTP2 for proxy-client to proxy-server #25
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #5
When proxy-client starts it will immediately make a connection to proxy-server, using HTTP2.
This connection will be used for all requests to that instance of proxy-client from the source client.
If proxy-client fails to send a request to the proxy-server because of a connection error, it will re-connect and do a new attestation verification.
Note that this does not re-use connections between proxy-server and the target service. Those are still one connection per request (but with minimal overhead since they don't use attested TLS).
Also, HTTP1.1 is still used for proxy-server to target service connections, as well as for source client to proxy-client.