Skip to content
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

Re-write TCP peek and tunnel logic #26

Closed
OlofBlomqvist opened this issue Oct 2, 2024 · 0 comments · Fixed by #37
Closed

Re-write TCP peek and tunnel logic #26

OlofBlomqvist opened this issue Oct 2, 2024 · 0 comments · Fixed by #37
Assignees
Labels
WIP Someone is working on this
Milestone

Comments

@OlofBlomqvist
Copy link
Owner

Today we peek incoming tcp streams and do an initial attempt at creating bidir tcp connection for tls and http connections, but in many cases where it would be possible to do the same if we just terminated the tls connection, we instead terminate the full http connection and create a new http(s) client for proxying a request via the tower hyper service and hyper legacy client. Would be nice to refactor this so that we can do tls termination without http termination for these cases.

It should be much faster for most cases and also provide an easier way to provide real-time traffic monitoring support.

@OlofBlomqvist OlofBlomqvist added this to the 0.2.0 milestone Oct 2, 2024
@OlofBlomqvist OlofBlomqvist self-assigned this Oct 2, 2024
@OlofBlomqvist OlofBlomqvist added the WIP Someone is working on this label Oct 2, 2024
@OlofBlomqvist OlofBlomqvist linked a pull request Oct 21, 2024 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
WIP Someone is working on this
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant