为什么 nginx 在域之前添加 %5C？答案

【问题标题】：Why nginx adds %5C before domain?为什么 nginx 在域之前添加 %5C？
【发布时间】：2016-05-27 02:19:33
【问题描述】：

我正在使用 Django 构建应用程序，最近我需要为多租户数据库实现子域，我使用子域作为租户标识符。

当我在服务器而不是 http://test1.example.com 上部署应用程序时，我在调试器中得到了这个 url http://%5Ctest1.example.com

即使我不请求子域也会发生同样的情况，即我输入 http://example.com，但调试器说请求的 url 是 http://%5Cexample.com

因为我使用子域作为标识符，这迫使我将 %5C（即反斜杠）添加到匹配表中。确实不是问题，但是很丑。

为什么会这样？是nginx故障还是其他原因？

如果重要的话我使用django-tenant-schemas，但我怀疑它会影响请求url，它只是从中获取子域名。

我的nginx配置（我用gunicorn）：

upstream example.com {
  # fail_timeout=0 means we always retry an upstream even if it failed
  # to return a good HTTP response (in case the Unicorn master nukes a
  # single worker for timing out).

  server unix:/home/webapps/bhc_virtualenv/run/gunicorn.sock fail_timeout=0;
}

upstream test1.example.com {
  # fail_timeout=0 means we always retry an upstream even if it failed
  # to return a good HTTP response (in case the Unicorn master nukes a
  # single worker for timing out).

  server unix:/home/webapps/bhc_virtualenv/run/gunicorn.sock fail_timeout=0;
}

upstream test2.example.com {
  # fail_timeout=0 means we always retry an upstream even if it failed
  # to return a good HTTP response (in case the Unicorn master nukes a
  # single worker for timing out).

  server unix:/home/webapps/bhc_virtualenv/run/gunicorn.sock fail_timeout=0;
}

server {

    listen   80;
    server_name example.com test1.example.com test2.example.com;

    client_max_body_size 4G;

    access_log /home/webapps/bhc_virtualenv/logs/nginx-access.log;
    error_log /home/webapps/bhc_virtualenv/logs/nginx-error.log;

    location /static/ {
        alias   /home/webapps/bhc_virtualenv/bhc1/static/;
    }

    location /media/ {
        alias   /home/webapps/bhc_virtualenv/bhc1/media/;
    }

    location / {
        # an HTTP header important enough to have its own Wikipedia entry:
        #   http://en.wikipedia.org/wiki/X-Forwarded-For
        proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;

        # enable this if and only if you use HTTPS, this helps Rack
        # set the proper protocol for doing redirects:
        # proxy_set_header X-Forwarded-Proto https;

        # pass the Host: header from the client right along so redirects
        # can be set properly within the Rack application
        proxy_set_header Host \$http_host;

        # we don't want nginx trying to do something clever with
        # redirects, we set the Host: header above already.
        proxy_redirect off;

        # set "proxy_buffering off" *only* for Rainbows! when doing
        # Comet/long-poll stuff.  It's also safe to set if you're
        # using only serving fast clients with Unicorn + nginx.
        # Otherwise you _want_ nginx to buffer responses to slow
        # clients, really.
        # proxy_buffering off;

        # Try to serve static files from nginx, no point in making an
        # *application* server like Unicorn/Rainbows! serve static files.
        if (!-f \$request_filename) {
            proxy_pass http://example.com;
            break;
        }
    }

    # Error pages
    error_page 500 502 503 504 /500.html;
    location = /500.html {
        root /home/webapps/bhc_virtualenv/bhc1/static/;
    }
}

【问题讨论】：

标签： django nginx deployment server subdomain

【解决方案1】：

%5C 是反斜杠 \ url 编码的。在您的 nginx 配置文件中，您不需要转义 $ 符号。

# remove the backslash
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

您需要删除配置中尝试转义$ 的所有反斜杠。使用您当前的配置，nginx 将带有反斜杠的 HTTP 标头传递给 Django，这会导致您在调试器中看到 URL。

【讨论】：