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
Edge-terminated routes allow you to set
insecureEdgeTerminationPolicytoredirect, 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 aredirectInsecureRequestsfield could be added?Version