You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
Edge-terminated routes allow you to set
insecureEdgeTerminationPolicy
toredirect
, 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 aredirectInsecureRequests
field could be added?Version
The text was updated successfully, but these errors were encountered: