Nginx不会从HTTPredirect到HTTPS

我的架构设置是在NodeJS的CentOS上运行的SSO服务，端口10102和10142，我需要所有端口80的请求redirect到443外部和内部我上游一切到NodeJS的上述端口，这里是我的configuration：

upstream sso1 { server localhost:10102; server localhost:10142; } server { listen [::]:80; listen 443 ssl; server_name www.site.business site.business; ssl_certificate /etc/nginx/cert.crt; ssl_certificate_key /etc/nginx/cert.key; ssl_session_cache builtin:1000 shared:SSL:10m; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4; ssl_prefer_server_ciphers on; if ($scheme = http) { return 301 https://$server_name$request_uri; } location / { proxy_pass http://sso1; proxy_read_timeout 90; proxy_redirect http://sso1 https://www.site.business; 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-Host $server_name; } } 

但无论我做什么，该网站仍然可以通过HTTP和HTTPS都可用。

任何想法为什么Nginx忽略我？ 我实际上已经尝试了不同的configuration，其中一个是捕获所有端口80的请求，301redirect它们：

 upstream sso1 { server localhost:10102; server localhost:10142; } server { listen [::]:80; server_name www.site.business site.business; return 301 https://$server_name$request_uri; } server { listen 443; server_name www.site.business site.business; ssl_certificate /etc/nginx/cert.crt; ssl_certificate_key /etc/nginx/cert.key; ssl on; ssl_session_cache builtin:1000 shared:SSL:10m; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4; ssl_prefer_server_ciphers on; location / { proxy_pass http://sso1; proxy_read_timeout 90; proxy_redirect http://sso1 https://www.site.business; 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-Host $server_name; } } 

• Nginx不区分大小写，区分大小写的proxy_pass
• caching控制no-cache，但不在Nginx的子文件夹中
• 是否有可能从PHP-FPM提供静态HTML？
• Nginx：括号语法的意义？
• 如何更改错误日志中的时间戳记格式？

 // Listen for requests for the main website server { server_name www.example.com; listen 443 ssl http2; // https optional, need to build Nginx with correct module ssl_certificatefullchain; ssl_certificate_key privkey; // locations etc } // Forward http requests for domain and www subdomain to main server { listen 80; server_name example.com www.example.com; return 301 https://www.example.com$request_uri; } // Forward https requests for root domain to main server { listen 443 ssl; server_name example.com; ssl_certificatefullchain; ssl_certificate_key privkey; return 301 https://www.example.com$request_uri; } 

 # This just prevents Nginx picking a random default server if it doesn't know which server block to send a request to server { listen 80 default_server; server_name _; return 444; # This means "go away", effectively }