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

Inital start to be able to redirect from http to https. #8258

Closed
wants to merge 1 commit into from
Closed

Inital start to be able to redirect from http to https. #8258

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Mar 28, 2016

See issue #5946
#5946

@openshift-bot openshift-bot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels May 1, 2016
@openshift-bot openshift-bot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels May 25, 2016
@openshift-bot openshift-bot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jun 10, 2016
@danmcp
Copy link
Contributor

danmcp commented Jun 14, 2016

@ramr @knobunc @openshift/api-review Review please.

@openshift-bot openshift-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 4, 2016
@openshift-bot
Copy link
Contributor

Origin Action Required: Pull request cannot be automatically merged, please rebase your branch from latest HEAD and push again

@openshift-bot openshift-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 4, 2016
// InsecureTerminationPolicy indicates the desired behavior for
// insecure connections to one of the tls (edge,passthrough,reencrypt) route:
// disable, allow or redirect
InsecureTerminationPolicy InsecureTerminationPolicyType
Copy link
Contributor

Choose a reason for hiding this comment

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

Why would we not just add "Redirect" to "InsecureEdgeTerminationPolicy"? I don't see the value in adding the new external field - we can just rename it in a future version. Broadening EdgeTerminationPolicy to apply to all termination types doesn't seem to have a disadvantage I can see. Examples?

Copy link
Contributor

Choose a reason for hiding this comment

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

#11953 is open to do just that.

@knobunc
Copy link
Contributor

knobunc commented Nov 18, 2016

@cw-aleks: Sorry, I missed this until today. I am closing in preference to #11953

Please tell me if that PR does not accommodate your needs.

@knobunc knobunc closed this Nov 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-api-review needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants