django + nginx https 重定向显示（414 Request-URI Too Large）答案

【问题标题】：django + nginx https redirect shows (414 Request-URI Too Large)django + nginx https 重定向显示（414 Request-URI Too Large）
【发布时间】：2018-04-19 23:07:20
【问题描述】：

我正在尝试解决 nginx 重定向到 https，但是当我使用 www.ozkandurakoglu.com 时，我收到 414 Request-URI Too Large 错误。这是我对 nginx 的设置：

upstream ozkan_server {
  server unix:/home/ytsejam/public_html/ozkansimple/run/gunicorn.sock fail_timeout=10s;
}

server {
    listen   80;
    server_name ozkandurakoglu.com www.ozkandurakoglu.com;
    return 301 $scheme:https://ozkandurakoglu.com$request_uri;
}
server {
  listen 443 ssl;
  listen [::]:443 ssl;
  ssl on;
  ssl_certificate /etc/letsencrypt/live/ozkandurakoglu.com/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/ozkandurakoglu.com/privkey.pem;
  ssl_trusted_certificate /etc/letsencrypt/live/ozkandurakoglu.com/chain.pem;
  ssl_session_timeout 1d;
  ssl_session_cache shared:SSL:50m;
  ssl_session_tickets off;
  ssl_prefer_server_ciphers on;
  add_header Strict-Transport-Security max-age=15768000;
  ssl_stapling on;
  ssl_stapling_verify on;
  server_name www.ozkandurakoglu.com;
  return 301 $scheme:https://ozkandurakoglu.com$request_uri;
}
server {
  listen 443 ssl;
  listen [::]:443 ssl;
  ssl on;
  ssl_certificate /etc/letsencrypt/live/ozkandurakoglu.com/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/ozkandurakoglu.com/privkey.pem;
  ssl_trusted_certificate /etc/letsencrypt/live/ozkandurakoglu.com/chain.pem;
  ssl_session_timeout 1d;
  ssl_session_cache shared:SSL:50m;
  ssl_session_tickets off;
  ssl_prefer_server_ciphers on;
  add_header Strict-Transport-Security max-age=15768000;
  ssl_stapling on;
  ssl_stapling_verify on;
  server_name  www.ozkandurakoglu.com ozkandurakoglu.com;
  client_max_body_size 4G;
  root /home/ytsejam/public_html/ozkansimple/;
  access_log /home/ytsejam/public_html/ozkansimple/logs/nginx-access.log;
  error_log /home/ytsejam/public_html/ozkansimple/logs/nginx-error.log warn;
  large_client_header_buffers 6 16k;
...
}

你能帮帮我吗？

谢谢

【问题讨论】：

应该是return 301 $scheme://ozkandurakoglu.com$request_uri 而不是return 301 $scheme:https://ozkandurakoglu.com$request_uri
它没有用...你有什么其他想法吗？
使用tarunlalwani.com/post/…调试出了什么问题
这是 gunicorn 的错误 .. 我们需要将此添加到 gunicorn start line => --limit-request-line INT ...
酷，您可以将其添加为答案。列出默认值是什么以及您对其进行了哪些更改。顺便说一句，这篇文章有帮助还是你自己找到的？

标签： django ssl nginx

【解决方案1】：

我回答我的问题是因为我必须更改我在问题中没有提到的 nginx 和 gunicorn，我在我的服务器块中删除了 $cheme

server {
    listen   80;
    server_name ozkandurakoglu.com www.ozkandurakoglu.com;
    return 301 https://ozkandurakoglu.com$request_uri;
}

并添加

limit_request_line

--limit-request-line INT
4094
The maximum size of HTTP request line in bytes.

到我的独角兽起跑线。

编辑：正确设置后的几天终于到了

server {
        listen 80;
        server_name ozkandurakoglu.com www.ozkandurakoglu.com;
        return 301 https://www.ozkandurakoglu.com$request_uri;
}
server {
    listen 443 ssl http2;
    server_name  ozkandurakoglu.com;
    return 301 https://www.ozkandurakoglu.com$request_uri;
}
server {
    listen 443 ssl http2;
    server_name  www.ozkandurakoglu.com;

    access_log /var/log/nginx/ozkandurakoglu.com.access.log;
    error_log /var/log/nginx/ozkandurakoglu.com.error.log;

    ssl_certificate         /etc/letsencrypt/live/www.ozkandurakoglu.com/fullchain.pem;
    ssl_certificate_key     /etc/letsencrypt/live/www.ozkandurakoglu.com/privkey.pem;
    ssl_trusted_certificate /etc/letsencrypt/live/www.ozkandurakoglu.com/chain.pem;

    ssl_session_timeout 1d;
    ssl_session_cache shared:SSL:64m;
    ssl_session_tickets off;

    ssl_protocols TLSv1.2;
    ssl_prefer_server_ciphers on;
    ssl_ciphers 'ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-$
    add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload";
    ssl_stapling on;
    ssl_stapling_verify on;
    add_header X-Frame-Options DENY;
    add_header X-Content-Type-Options "nosniff" always;
    add_header X-XSS-Protection "1; mode=block";
    add_header Referrer-Policy no-referrer-when-downgrade;
    #add_header Content-Security-Policy "default-src https:";

    resolver 8.8.8.8 8.8.4.4;
    resolver_timeout 5s;

  client_max_body_size 4G;

... }

【讨论】：