make port 80 redirect to SSL #108
Conversation
These days it's generally accepted that best practice is to use SSL everywhere, since unencrypted traffic is susceptible to all kinds of security and privacy issues.
It was a mix of tabs and spaces, and the tabs were obviously meant to be interpreted as being 4 columns wide, which is a much less common interpretation than 8 columns. So make the file self-consistent and unambiguous by replacing each tab with 4 spaces.
|
@aspiers many users prefer use an reverse proxy like traefik or jwilder-nginx-proxy |
|
@luizeof This docker-compose.yml file already sets up nginx as a reverse proxy so I'm not sure what your point is here, or how that's related to this PR? |
|
Hi @aspiers you can use the image https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion side by side within nginx-proxy ... this image provide the necessary let's encrypt features to nginx-proxy |
|
@luizeof Thanks for the link. I already used this one to get letsencrypt set up. I still don't understand setting up letsencrypt or your previous comment about reverse proxies relate to this PR though. This PR is simply about redirecting from non-SSL to SSL, which is best practice in every case, independently of how SSL is implemented. |
These days it's generally accepted that best practice is to use SSL
everywhere, since unencrypted traffic is susceptible to all kinds of
security and privacy issues.