从 2 天前开始,nginx 开始支持 websocket 连接,因此我尝试让我的 nginx-nodejs-socket.io 应用程序在没有 HAproxy 等的情况下工作(但运气不佳)。
我真正想要实现的是 nginx 只向后端服务器或 websocket 服务器(更准确地说是 socket.io)发送 websocket 连接请求,同时 nginx 将提供 php 文件和所有静态内容(包括 html 文件)。我根本不希望 express 提供静态内容(如果可能的话)。
这是我的 nginx.conf
#user nobody;
worker_processes 1;
#error_log logs/error.log;
#error_log logs/error.log notice;
#error_log logs/error.log info;
#pid logs/nginx.pid;
events {
worker_connections 1024;
}
http {
include mime.types;
default_type application/octet-stream;
#log_format main '$remote_addr - $remote_user [$time_local] "$request" '
# '$status $body_bytes_sent "$http_referer" '
# '"$http_user_agent" "$http_x_forwarded_for"';
#access_log logs/access.log main;
sendfile on;
#tcp_nopush on;
#keepalive_timeout 0;
keepalive_timeout 65;
gzip on;
upstream backend {
server 127.0.0.1:8080;
}
server {
listen 80;
server_name localhost;
charset UTF-8;
#access_log logs/host.access.log main;
location / {
root /website/html_public;
index index.php index.html index.htm;
}
#error_page 404 /404.html;
# redirect server error pages to the static page /50x.html
#
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /website/html_public;
}
# proxy the PHP scripts to Apache listening on 127.0.0.1:80
#
#location ~ \.php$ {
# proxy_pass http://127.0.0.1;
#}
# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
location ~ \.php$ {
root /website/html_public;
try_files $uri =404;
fastcgi_pass unix:/tmp/php5-fpm.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include fastcgi_params;
}
# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
location ~ /\.ht {
deny all;
}
location /connection {
proxy_pass http://backend;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
}
# another virtual host using mix of IP-, name-, and port-based configuration
#
#server {
# listen 8000;
# listen somename:8080;
# server_name somename alias another.alias;
# location / {
# root /website/html_public;
# index index.php index.html index.htm;
# }
#}
}
下面是我的节点中的 server.js 文件
var express = require('express');
var app = express();
var port = 8080;
/* HTTP Server*/
server = require('http').createServer(app);
server.listen(port);
app.use(express.logger(':remote-addr - :method :url HTTP/:http-version :status :res[content-length] - :response-time ms'));
app.use(express.static(__dirname + '/html_public'));
app.use(express.favicon());
app.set('view engine', 'jade');
app.set('view options', { layout: false });
app.set('views', __dirname + '/views');
app.get('/', function(req, res){
res.render('index.html');
});
/*
* Web Sockets
*/
io = require('socket.io').listen(server),
io.configure('production', function(){
io.enable('browser client etag');
io.set('log level', 1);
io.set('transports', [ 'websocket', 'htmlfile', 'xhr-polling', 'jsonp-polling' ]);
});
console.log('Chat Server started with Node '+ process.version +', platform '+ process.platform + 'to port %d',port);
从我的客户端尝试如下连接:
socket = new io.connect('http://localhost/connection');
问题是,当我尝试正常连接时,在 chrome 浏览器中输入 localhost,我在控制台上看到:
GET http://localhost/socket.io/socket.io.js 404 (Not Found)
并且在浏览器中输入时:http://localhost/connection
我收到“无法获取/连接“这告诉我,使用我当前的配置,nginx 没有正常代理 websocket。
答案1
好的,通过 nginx 的 websockets 已经工作了”
我将位置部分更改为:
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_set_header X-NginX-Proxy true;
proxy_pass http://backend;
proxy_redirect off;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
现在它可以建立非常快的网络套接字连接。耶!
答案2
socket.io 有点狡猾,它会从其 node_modules 目录中的某个地方自动提供客户端脚本 socket.io.js。
因此,您需要做的是告诉 nginx 将该位置的请求也传递给您的 node.js。在我的 nginx.conf 中,我有:
location /chat {
proxy_pass http://backend;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
location /socket.io {
proxy_pass http://backend;
}
然而,这只能让我走到这一步,然后 websocket 连接就会失败,并出现 502“坏网关”错误。
此后,socket.io 又会回到 xhr-polling,速度非常非常慢。