|
|
|
map $http_upgrade $connection_upgrade {
|
|
|
|
default upgrade;
|
|
|
|
'' close;
|
|
|
|
}
|
|
|
|
|
|
|
|
upstream backend {
|
|
|
|
server 127.0.0.1:3000 fail_timeout=0;
|
|
|
|
}
|
|
|
|
|
|
|
|
upstream streaming {
|
|
|
|
server 127.0.0.1:4000 fail_timeout=0;
|
|
|
|
}
|
|
|
|
|
|
|
|
proxy_cache_path /var/cache/nginx levels=1:2 keys_zone=CACHE:10m inactive=7d max_size=1g;
|
|
|
|
|
|
|
|
server {
|
|
|
|
listen 80;
|
|
|
|
listen [::]:80;
|
|
|
|
server_name example.com;
|
|
|
|
root /home/mastodon/live/public;
|
|
|
|
location /.well-known/acme-challenge/ { allow all; }
|
|
|
|
location / { return 301 https://$host$request_uri; }
|
|
|
|
}
|
|
|
|
|
|
|
|
server {
|
|
|
|
listen 443 ssl http2;
|
|
|
|
listen [::]:443 ssl http2;
|
|
|
|
server_name example.com;
|
|
|
|
|
|
|
|
ssl_protocols TLSv1.2 TLSv1.3;
|
|
|
|
ssl_ciphers HIGH:!MEDIUM:!LOW:!aNULL:!NULL:!SHA;
|
|
|
|
ssl_prefer_server_ciphers on;
|
|
|
|
ssl_session_cache shared:SSL:10m;
|
|
|
|
ssl_session_tickets off;
|
|
|
|
|
|
|
|
# Uncomment these lines once you acquire a certificate:
|
|
|
|
# ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
|
|
|
|
# ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
|
|
|
|
|
|
|
|
keepalive_timeout 70;
|
|
|
|
sendfile on;
|
|
|
|
client_max_body_size 80m;
|
|
|
|
|
|
|
|
root /home/mastodon/live/public;
|
|
|
|
|
|
|
|
gzip on;
|
|
|
|
gzip_disable "msie6";
|
|
|
|
gzip_vary on;
|
|
|
|
gzip_proxied any;
|
|
|
|
gzip_comp_level 6;
|
|
|
|
gzip_buffers 16 8k;
|
|
|
|
gzip_http_version 1.1;
|
|
|
|
gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript image/svg+xml image/x-icon;
|
|
|
|
|
Make sure nginx always send HSTS header (#16633)
By default, it'll only send those headers when the response code is one of the following:
- 200, 201, 204, 206, 301, 302, 303, 304, 307 & 308
As all the traffics should be https, the http protocol only exists to do 301 redirect,
and always send the HSTS header is almost one of the best practices, we should set
nginx to do so.
Reference:
- https://nginx.org/en/docs/http/ngx_http_headers_module.html#add_header
- https://ssl-config.mozilla.org/
3 years ago
|
|
|
add_header Strict-Transport-Security "max-age=31536000" always;
|
|
|
|
|
|
|
|
location / {
|
|
|
|
try_files $uri @proxy;
|
|
|
|
}
|
|
|
|
|
|
|
|
location ~ ^/(emoji|packs|system/accounts/avatars|system/media_attachments/files) {
|
|
|
|
add_header Cache-Control "public, max-age=31536000, immutable";
|
Make sure nginx always send HSTS header (#16633)
By default, it'll only send those headers when the response code is one of the following:
- 200, 201, 204, 206, 301, 302, 303, 304, 307 & 308
As all the traffics should be https, the http protocol only exists to do 301 redirect,
and always send the HSTS header is almost one of the best practices, we should set
nginx to do so.
Reference:
- https://nginx.org/en/docs/http/ngx_http_headers_module.html#add_header
- https://ssl-config.mozilla.org/
3 years ago
|
|
|
add_header Strict-Transport-Security "max-age=31536000" always;
|
|
|
|
try_files $uri @proxy;
|
|
|
|
}
|
|
|
|
|
|
|
|
location /sw.js {
|
|
|
|
add_header Cache-Control "public, max-age=0";
|
Make sure nginx always send HSTS header (#16633)
By default, it'll only send those headers when the response code is one of the following:
- 200, 201, 204, 206, 301, 302, 303, 304, 307 & 308
As all the traffics should be https, the http protocol only exists to do 301 redirect,
and always send the HSTS header is almost one of the best practices, we should set
nginx to do so.
Reference:
- https://nginx.org/en/docs/http/ngx_http_headers_module.html#add_header
- https://ssl-config.mozilla.org/
3 years ago
|
|
|
add_header Strict-Transport-Security "max-age=31536000" always;
|
|
|
|
try_files $uri @proxy;
|
|
|
|
}
|
|
|
|
|
|
|
|
location @proxy {
|
|
|
|
proxy_set_header Host $host;
|
|
|
|
proxy_set_header X-Real-IP $remote_addr;
|
|
|
|
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
|
|
|
|
proxy_set_header X-Forwarded-Proto $scheme;
|
|
|
|
proxy_set_header Proxy "";
|
|
|
|
proxy_pass_header Server;
|
|
|
|
|
|
|
|
proxy_pass http://backend;
|
|
|
|
proxy_buffering on;
|
|
|
|
proxy_redirect off;
|
|
|
|
proxy_http_version 1.1;
|
|
|
|
proxy_set_header Upgrade $http_upgrade;
|
|
|
|
proxy_set_header Connection $connection_upgrade;
|
|
|
|
|
|
|
|
proxy_cache CACHE;
|
|
|
|
proxy_cache_valid 200 7d;
|
|
|
|
proxy_cache_valid 410 24h;
|
|
|
|
proxy_cache_use_stale error timeout updating http_500 http_502 http_503 http_504;
|
|
|
|
add_header X-Cached $upstream_cache_status;
|
Make sure nginx always send HSTS header (#16633)
By default, it'll only send those headers when the response code is one of the following:
- 200, 201, 204, 206, 301, 302, 303, 304, 307 & 308
As all the traffics should be https, the http protocol only exists to do 301 redirect,
and always send the HSTS header is almost one of the best practices, we should set
nginx to do so.
Reference:
- https://nginx.org/en/docs/http/ngx_http_headers_module.html#add_header
- https://ssl-config.mozilla.org/
3 years ago
|
|
|
add_header Strict-Transport-Security "max-age=31536000" always;
|
|
|
|
|
|
|
|
tcp_nodelay on;
|
|
|
|
}
|
|
|
|
|
|
|
|
location /api/v1/streaming {
|
|
|
|
proxy_set_header Host $host;
|
|
|
|
proxy_set_header X-Real-IP $remote_addr;
|
|
|
|
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
|
|
|
|
proxy_set_header X-Forwarded-Proto $scheme;
|
|
|
|
proxy_set_header Proxy "";
|
|
|
|
|
|
|
|
proxy_pass http://streaming;
|
|
|
|
proxy_buffering off;
|
|
|
|
proxy_redirect off;
|
|
|
|
proxy_http_version 1.1;
|
|
|
|
proxy_set_header Upgrade $http_upgrade;
|
|
|
|
proxy_set_header Connection $connection_upgrade;
|
|
|
|
|
|
|
|
tcp_nodelay on;
|
|
|
|
}
|
|
|
|
|
|
|
|
error_page 500 501 502 503 504 /500.html;
|
|
|
|
}
|