-
Notifications
You must be signed in to change notification settings - Fork 28
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
tunneldriver: use the ngrok-go provided forwarding mechanism #324
Conversation
Current dependencies on/for this PR: This stack of pull requests is managed by Graphite. |
150a056
to
ce9a015
Compare
go.mod
Outdated
github.com/stretchr/testify v1.8.1 | ||
golang.ngrok.com/ngrok v1.4.0 | ||
github.com/stretchr/testify v1.8.4 | ||
golang.ngrok.com/ngrok v1.6.1-0.20231129180200-b8b5d7fcf1d0 |
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.
Is this pointing to ngrok-go/main
?
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.
Yeah - probably doesn't need to though. Pretty sure this feature is released.
Ugh, I forgot that we haven't added the options for making the forwarding TLS config use Back to draft it goes. |
@jrobsonchase what are the next steps on this ticket? |
47f96e2
to
681df85
Compare
681df85
to
9f5aa46
Compare
@jonstacks @deroine @alex-bezek heads up we're closing this for cleanup, feel free to reopen if it's still needed. |
What
Use the upstream
ListenAndForward
API instead of reimplementing the connection join logic.This also lets us lean on the upstream TLS terminating semantics and (soon) its HTTP/2 interaction with TLS.
How
Remove
handleConns
andhandleConn
in favor of thengrok-go
provided API.Breaking Changes
None