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

Support HTTP->HTTPS redirection on non-edge terminated routes #11547

Closed
elyscape opened this issue Oct 24, 2016 · 1 comment
Closed

Support HTTP->HTTPS redirection on non-edge terminated routes #11547

elyscape opened this issue Oct 24, 2016 · 1 comment

Comments

@elyscape
Copy link
Contributor

Edge-terminated routes allow you to set insecureEdgeTerminationPolicy to redirect, which makes causes the router to respond to HTTP requests with 302 Found and a redirect to the same location over HTTPS. If, however, you're using a reencrypt or passthrough route, this is not an option. While it would be relatively simple to set up another, HTTP-only route pointing at a service that used nginx to respond to all requests with a redirect to HTTPS, this seems like the sort of thing that could be trivially handled by the router. Maybe a redirectInsecureRequests field could be added?

Version
oc v1.3.1
kubernetes v1.3.0+52492b4
features: Basic-Auth

Server [REMOVED]
openshift v1.3.0
kubernetes v1.3.0+52492b4
@knobunc
Copy link
Contributor

knobunc commented Oct 25, 2016

This is https://trello.com/c/0BaxAOK9 and there's bug https://bugzilla.redhat.com/show_bug.cgi?id=1306216 open too. We are working on it.

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

No branches or pull requests

4 participants