Skip to content

https+tcp+sni listener support#784

Merged
nathanejohnson merged 1 commit into
fabiolb:masterfrom
nathanejohnson:feature/httpstcpsni
Sep 3, 2020
Merged

https+tcp+sni listener support#784
nathanejohnson merged 1 commit into
fabiolb:masterfrom
nathanejohnson:feature/httpstcpsni

Conversation

@nathanejohnson

@nathanejohnson nathanejohnson commented Aug 28, 2020

Copy link
Copy Markdown
Member

Adds support for the https+tcp+sni listener. Any host routes that are marked with
proto=tcp or have a scheme tcp:// will be matched for TCP SNI steering. Failing
any matches there, fallthrough will be to https matching. This resolves: #783.

clean up error handling on 'use of closed network connection' case

fix makefile tag finding stuff

fix logic for https+tcp+sni matching so that only explicit proto=tcp matches

@nathanejohnson nathanejohnson force-pushed the feature/httpstcpsni branch 2 times, most recently from 259b023 to 9f92192 Compare August 28, 2020 20:47
@nathanejohnson nathanejohnson added this to the 1.5.14 milestone Aug 28, 2020
@nathanejohnson nathanejohnson force-pushed the feature/httpstcpsni branch 6 times, most recently from 7f1f8f2 to 0cbf12c Compare August 30, 2020 17:14
@nathanejohnson

nathanejohnson commented Aug 31, 2020

Copy link
Copy Markdown
Member Author

I'll give this a few days, failing any negative reviews I'm merging this. So deadline is September 2 to voice concerns

@dcarbone dcarbone left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, only actual problem i see is unbuffered errChan in .Close(), unless there is a reason for it to be unbuffered that i'm unaware of.

Comment thread proxy/inetaf_tcpproxy.go Outdated
Comment thread proxy/inetaf_tcpproxy.go Outdated
Comment thread proxy/inetaf_tcpproxy.go Outdated
Comment thread proxy/inetaf_tcpproxy_integration_test.go Outdated
Comment thread .travis.yml Outdated
Adds support for the https+tcp+sni listener.  Any routes that are marked with
proto=tcp or have a scheme tcp:// will be matched for TCP steering.  Failing
any matches there, fallthrough will be to https matching.  This resolves: fabiolb#783.

clean up error handling on 'use of closed network connection' case

fix makefile tag finding stuff

fix logic for https+tcp+sni matching so that only explicit proto=tcp matches

Adding an integration test

make sure proxy is listening before starting test

add buffered err chan to Close() per dcarbone

add 1.14 and 1.15 to travis tests

@dcarbone dcarbone left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add support for HTTPS+TCP+SNI on the same listener

2 participants