example.com 與 www.example.com 內容重複server {
listen 80;
server_name example.com; # 裸域名
# 301 永久重導向至 www
if ($host != 'www.example.com') {
rewrite ^/(.*)$ https://www.example.com/$1 permanent;
}
}
| 指令 | 說明 |
|---|---|
permanent | 回傳 HTTP 301 (Moved Permanently),瀏覽器/搜尋引擎會更新書籤/索引 |
redirect | 回傳 HTTP 302 (Found),臨時重導向,不傳遞權重 |
$host | 請求的 Host 標頭 (不含埠號) |
rewrite ^/(.*)$ ... | 捕獲完整路徑並保留至目標 URL |
server {
listen 80;
server_name example.com;
return 301 https://www.example.com$request_uri;
}
server {
listen 80;
server_name www.example.com;
# 實際站點配置...
}
return 301 效能優於 rewrite,語意更清晰,官方推薦做法。
# HTTP 裸域名 → HTTPS www
server {
listen 80;
server_name example.com;
return 301 https://www.example.com$request_uri;
}
# HTTP www → HTTPS www
server {
listen 80;
server_name www.example.com;
return 301 https://www.example.com$request_uri;
}
# HTTPS www 實際站點
server {
listen 443 ssl http2;
server_name www.example.com;
ssl_certificate /path/fullchain.pem;
ssl_certificate_key /path/privkey.pem;
# ... 站點配置
}
curl -I https://example.com
# HTTP/1.1 301 Moved Permanently
# Location: https://www.example.com/
curl -I https://www.example.com
# HTTP/1.1 200 OK
server 區塊同時監聽裸域名與 www → 無限迴圈@ A 記錄 與 www CNAME/A 記錄redirect (302) 導致 SEO 權重不傳遞