Hello Moshe,
Thank you very much for your quick and detailed answer.
Have a nice day !
Le dimanche 2 décembre 2018 à 23:57:25 UTC+1, Moshe Katz
a écrit :
Here is a sample working configuration from one of my servers. Note that it
uses separate `server` blocks for HTTP and HTTPS to ma
Here is a sample working configuration from one of my servers. Note that it
uses separate `server` blocks for HTTP and HTTPS to make it easier to read.
server {
listen 80;
listen [::]:80;
server_name server.example.com;
location ~ /\.well-known {
ro
I believe you need to put the `return 301 ...` inside a location block too.
Otherwise, it overrides all the location blocks.
I'm on my phone now, but I'll try to share a sample file from one of my
servers (that works as you want it) when I get back to my computer.
Moshe
On Sun, Dec 2, 2018, 5:0
Hello,
I'd like to be able to offer let's encrypt in port 80 only and redirect
everything else to port 443
server {
listen 80;
listen [::]:80;
listen 443;
listen [::]:443;
server_name http://www.mydomain.org blog.mydomain.org;
location ^~ /.well-kn
We all know that the cache feature in Nginx will cache all response content
generated by upstream server. But I wonder whether there is a solution that
only the response body is cached by Nginx while some response headers should
not be cached and should be sent to client directly .I know that Ng
