redirect HTTPS traffic to HTTPS #85
Conversation
missytake
force-pushed
the
https-redirect
branch
from
f439821
to
0af41d3
Compare
|
To verify this works, run:
and compare it to the status quo (or rather, the state of #75):
|
| listen [::]:80 default_server; | ||
| server_name _; | ||
|
|
||
| return 301 https://$host$request_uri; |
There was a problem hiding this comment.
Does this work with letsencrypt queries?
There was a problem hiding this comment.
Pretty sure, because that's also what we use at other nginx servers, but we can try it with c4.testrun.org.
There was a problem hiding this comment.
At least some of our nginx servers use acmetool in redirector mode where it serves HTTP for challenges and HTTP-to-HTTPS redirects.
But Let's Encrypt says it follows redirects, so this setup should work: https://letsencrypt.org/docs/challenge-types/#http-01-challenge
missytake
force-pushed
the
https-redirect
branch
from
0af41d3
to
0c43449
Compare
fix #81
After we merged #75 we should rebase this (or the other way round), as nginx.conf is changed there as well.