如何解決這個Nginx配置來正確代理WebSocket請求而不是返回301？

Nginx noob。嘗試將Nginx配置爲在另一個運行於http://localhost:8082的Web服務器之前充當SSL代理服務器。也就是說，我希望所有http://localhost的請求都被重定向到https://localhost。這部分工作得很好。如何解決這個Nginx配置來正確代理WebSocket請求而不是返回301？

問題是，端口8082上的應用程序也使用WebSocket連接ws://localhost:8082/public-api/repossession-requests-socket。我試圖將任何連接重定向到ws://localhost/public-api/repossession-requests-socket到wss://localhost/public-api/repossession-requests-socket，並讓Nginx代理那些WebSocket請求到ws://localhost:8082/public-api/repossession-requests-socket。

相反，WebSocket的連接失敗，因爲Nginx的是爲都ws://localhost/public-api/repossession-requests-socket & wss://localhost/public-api/repossession-requests-socket返回301。我的配置如下;我在我的測試中使用Docker鏡像nginx:alpine（$PWD映射到/app）。

我該如何改變這一點，以便我不再看到301s？

events { 
    worker_connections 1024; 
} 

http { 
    server { 
     listen 80; 
     return 301 https://$host$request_uri; 
    } 

    server { 
     listen 443; 
     server_name localhost; 

     ssl_certificate /app/docker/public.pem; 
     ssl_certificate_key /app/docker/private.pem; 

     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; 

     access_log /app/access-443.log; 

     location/{ 
      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_pass http://localhost:8082; 
      proxy_read_timeout 90; 

      proxy_redirect http://localhost:8082 https://localhost; 
     } 
     location /public-api/repossession-requests-socket/ { 
      proxy_pass http://localhost:8082; 
      proxy_http_version 1.1; 
      proxy_set_header Upgrade $http_upgrade; 
      proxy_set_header Connection "upgrade"; 
     } 
    } 
}

來源

2016-11-15 Matthew Adams