nginx 为什么所有路由都有效，但一个是“301 Moved Permanently”？

Question

我问过类似的问题，但没有成功。

假设我有两个 node.js 应用程序正在打开服务器：

// App GoodMorning
var express     = require('express');

app.post('/breakfast', function (req, res) {  
    console.log("Eating breakfast");
    res.sendStatus(200);
});

app.get('/', function (req, res) {
    res.send('GoodMorning');
});

app.listen(3000, function () {
  console.log('GoodMorning app listening on port 3000!');
});

和

// App GoodEvening
var express     = require('express');

app.post('/diner', function (req, res) {  
    console.log("Eating diner");
    res.sendStatus(200);
});

app.get('/', function (req, res) {
    res.send('GoodEvening');
});

app.listen(4000, function () {
  console.log('GoodEvening app listening on port 4000!');
});

假设 Nginx 被用作反向代理服务器。所以它必须将请求发送到正确的端口，对吗？所以“魔法”文件是这样的：

# HTTP - redirect all requests to HTTPS:
server {
    listen 80;
    listen [::]:80 default_server ipv6only=on;
    return 301 https://$host$request_uri;
}


# HTTPS - proxy requests on to local Node.js app:
server {
    listen 443;
    server_name iamhungry.com;

    ssl on;
    # Use certificate and key provided by Let's Encrypt:
    ssl_certificate /etc/letsencrypt/live/iamhungry.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/iamhungry.com/privkey.pem;
    ssl_session_timeout 5m;
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_prefer_server_ciphers on;
    ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';

    # Pass requests for / to localhost:3000:
    location / {
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-NginX-Proxy true;
            proxy_pass http://localhost:3000/;
            proxy_ssl_session_reuse off;
            proxy_set_header Host $http_host;
            proxy_cache_bypass $http_upgrade;
            proxy_redirect off;
    }

    # Pass requests for /homepageevening to localhost:4000:
    location /homepageevening {
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-NginX-Proxy true;
            proxy_pass http://localhost:4000/;
            proxy_ssl_session_reuse off;
            proxy_set_header Host $http_host;
            proxy_cache_bypass $http_upgrade;
            proxy_redirect off;
    }

    # Pass requests for /diner to localhost/diner:4000:
    location /diner {
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-NginX-Proxy true;
            proxy_pass http://localhost/diner:4000/;
            proxy_ssl_session_reuse off;
            proxy_set_header Host $http_host;
            proxy_cache_bypass $http_upgrade;
            proxy_redirect off;
    }

}

那么下面的请求会产生如下的结果：

$ curl iamhungry.com 
$ GoodMorning // OK

$ curl -X POST iamhungry.com/breakfast
--> I see "Eating brakfast" in the log file of breakfast.js // OK


$ curl iamhungry.com/homepageevening
$ GoodEvening // OK

$ curl -X POST iamhungry.com/diner -I
HTTP/1.1 301 Moved Permanently // why ?!
--> And I see nothing in the log file of evening.js // why ?!

我对这些代理概念并不放心。我浏览了 nginx 的文档，但没有找到任何帮助。我想知道我理解它的工作方式的方式是否正确。

Answer 1

好的，谢谢@RichardSmith。我必须修复配置文件：

  location /diner {
        ...
        proxy_pass http://localhost:4000/diner;

并使用curl http://iamhungry.com -I -L 而不是curl http://iamhungry.com -I 进行测试，以实际遵循重新路由。

这是我所缺少的：

1. 301 不是错误。我正在使用curl http://iamhungry.com -I 在终端中进行测试，但使用选项 -L curl http://iamhungry.com -I -L 允许我遵循重定向然后到达行尾！所以 301 其实使用 nginx 是正常的，因为重定向是它的作用。

2. 端口号附加到域名。谢谢@RichardSmith。

3. 来自@RichardSmith 链接：[...]与位置匹配的规范化请求 URI 部分被指令中指定的 URI 替换。