代码之家  ›  专栏  ›  技术社区  ›  Mark J Miller

使用proxy_pass的nginx重定向

  •  1
  • Mark J Miller  · 技术社区  · 8 年前

    我有一个在本地机器上运行的nginx代理服务器配置。它正在docker中运行,节点也是。js实例,它为我的ghost博客的本地实例提供服务。

    因为我刚从旧的博客引擎迁移过来,我的url现在不同了,所以我想配置nginx以返回301(永久)重定向到新的url方案。我试过同时使用 rewrite proxy_redirect 在这两种情况下,我都有401个错误。这是我的default.conf

    # If we receive X-Forwarded-Proto, pass it through; otherwise, pass along the
    # scheme used to connect to this server
    map $http_x_forwarded_proto $proxy_x_forwarded_proto {
      default $http_x_forwarded_proto;
      ''      $scheme;
    }
    # If we receive Upgrade, set Connection to "upgrade"; otherwise, delete any
    # Connection header that may have been passed to this server
    map $http_upgrade $proxy_connection {
      default upgrade;
      '' close;
    }
    gzip_types text/plain text/css application/javascript application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;
    log_format vhost '$host $remote_addr - $remote_user [$time_local] '
                     '"$request" $status $body_bytes_sent '
                     '"$http_referer" "$http_user_agent"';
    access_log off;
    # HTTP 1.1 support
    proxy_http_version 1.1;
    proxy_buffering off;
    proxy_set_header Host $http_host;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $proxy_connection;
    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 $proxy_x_forwarded_proto;
    server {
        server_name _; # This is just an invalid value which will never trigger on a real hostname.
        listen 80;
        access_log /var/log/nginx/access.log vhost;
        return 503;
    }
    upstream localhost {
        server 172.17.0.3:2368;
    }
    server {
        server_name localhost;
        listen 80;
        access_log /var/log/nginx/access.log vhost;
        location / {
    #        rewrite "^/archive/(\d{4}/\d{2}/\d{2}/.+)\.(?:aspx|html)$" /$1 break; 
            proxy_pass http://localhost;
    #        proxy_redirect "-*/archive/(\d{4}/\d{2}/\d{2}/.+)\.(?:aspx|html)" /$1;
        }
    }
    

    如果我取消对rewrite或proxy_redirect指令的注释,则不会发生任何事情-请求将被转发到节点。js,我得到一个404。

    如果我像这样使用多个位置指令:

    location /archive/ {
        rewrite "^/archive/(\d{4}/\d{2}/\d{2}/.+)\.(?:aspx|html)$" /$1 break; 
    }    
    location / {
        proxy_pass http://localhost;
    }
    

    我从nginx得到了一个404,这个请求永远不会发送到node.js。

    1 回复  |  直到 8 年前
        1
  •  0
  •   Richard Smith    8 年前

    你的 rewrite 在单独的位置块中,应使用 last 而不是 break (参见 this 详细信息):

    location /archive/ {
        rewrite "^/archive/(\d{4}/\d{2}/\d{2}/.+)\.(?:aspx|html)$" /$1 last;
    }  
    

    proxy_redirect 不重写请求,它重写来自上游的3xx响应。看见 this 详细信息。

    我看不出你俩有什么问题 重写 方法,除非正则表达式是错误的。你可以尝试添加 rewrite_log on; 以逐步记录重写。看见 this 详细信息。