Shulou(Shulou.com)06/03 Report--

Since there is usually a cross-domain problem, the cross-domain is also configured directly. For more information on cross-domain configuration of Nginx, please refer to my previous article: Nginx configuration cross-domain request

Reverse proxy configuration for websocket:

Post the code directly:

Server {listen 9000; # listening on port 9000 server_name websocket_server; # allowing cross-domain add_header Access-Control-Allow-Origin *; add_header Access-Control-Allow-Methods' GET, POST, OPTIONS'; add_header Access-Control-Allow-Headers' DNT,X-Mx-ReqToken,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization' If ($request_method = 'OPTIONS') {return 204;} location / {# add wensocket proxy proxy_pass http://127.0.0.1:9093; # websocket server. Never mind ws:// proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade";}}

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.