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

internal/dag: permit combining non tls routing with tcp proxy #1450

Merged
merged 1 commit into from
Sep 5, 2019

Conversation

davecheney
Copy link
Contributor

Fixes #910

The use case is for a service offering tls passthrough on port 443, the
same service may wish to offer a non tls port which informs users they
need to connect over port 443. Presumably port 443 is not HTTPS but some
other protocol, the port 80 fallback is a convenience for people typing
the address into their browsers.

Signed-off-by: Dave Cheney dave@cheney.net

Fixes projectcontour#910

The use case is for a service offering tls passthrough on port 443, the
same service may wish to offer a non tls port which informs users they
need to connect over port 443. Presumably port 443 is not HTTPS but some
other protocol, the port 80 fallback is a convenience for people typing
the address into their browsers.

Signed-off-by: Dave Cheney <dave@cheney.net>
@davecheney davecheney added this to the 1.0.0-beta.1 milestone Sep 5, 2019
Copy link
Member

@stevesloka stevesloka left a comment

Choose a reason for hiding this comment

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

/lgtm

@davecheney davecheney merged commit b070523 into projectcontour:master Sep 5, 2019
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.

TLS Passthrough & HTTP Redirect
2 participants