[WIP] Add an auto-redirect for all HTTP to HTTPs #94
Conversation
First attempt at introducing a TLS-redirect at the ALB layer (so that none of our services need to be aware of this)
|
@MikeTheCanuck , one question I would have is how are health checks configured?, would endpoints returning a 301 affect these? We may also need to verify any test suites that are calling http endpoints |
|
Good ideas to verify these behaviours. I'm 90% sure that the health check call from ALB to the container would happen after the layer that performs this redirect. It will be very easy to check, just looking at the CloudWatch logs for Django will tell us instantly whether the requests are getting to the containers, and if they're happening once or twice. I don't know as much about any application test suites, and which of them to evaluate where to know if this has affected anything or not. Can you help track them down, and maybe even boil down to a list of (a) where to look, (b) what to look for, for each of the applications? |
Addresses hackoregon/civic-devops#215
Adds a TLS-redirect at the ALB layer, so that none of our services need to be aware of HTTP/HTTPS distinctions. At present, would affect all HTTP resources under the civicpdx.org, service.civicpdx.org and civicplatform.org domains.