Question

我正在用Gunicorn托管Django应用。发生的情况如下

来自Django的示例响应如下

@require_http_methods(['POST'])
def register(request):

    body = json.loads(request.body.decode('utf-8'))

    try:
        email = body['email']
    except:
        return HttpResponse(status=400, reason="Email must be provided.")

在开发过程中，Django应用程序使用命令python manage.py runserver运行，并且完全没有问题。它总是以

响应

400 Email must be provided

但是，在生产环境中，其托管方式如下

Procfile

web: gunicorn app.wsgi
release: python manage.py migrate

wsgi.py

import os

from django.core.wsgi import get_wsgi_application

os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'app.settings')

application = get_wsgi_application()

但是，在发出请求时，响应如下。

400

我错过了不能正确转发原因的地方吗？

*编辑1

生产与开发之间也存在差异，即在生产环境中，古尼康住在没有开发的nginx后面。 Nginx导致的问题可能不转发本地原因阶段，如果是，是否可以更改它？

*编辑2

下面是我的nginx.conf

server {
  listen      [::]:80;
  listen      80;
  server_name api.app.com; 
  access_log  /var/log/nginx/app-access.log;
  error_log   /var/log/nginx/app-error.log;

  return 301 https://$host:443$request_uri;

}

server {
  listen      [::]:443 ssl http2;
  listen      443 ssl http2;

  server_name api.app.com; 
  access_log  /var/log/nginx/app-access.log;
  error_log   /var/log/nginx/app-error.log;

  ssl_certificate           /home/dokku/app/tls/server.crt;
  ssl_certificate_key       /home/dokku/app/tls/server.key;
  ssl_protocols             TLSv1.2 TLSv1.3;
  ssl_prefer_server_ciphers off;

  keepalive_timeout   70;


  location    / {

    gzip on;
    gzip_min_length  1100;
    gzip_buffers  4 32k;
    gzip_types    text/css text/javascript text/xml text/plain text/x-component application/javascript application/x-javascript application/json application/xml  application/rss+xml font/truetype application/x-font-ttf font/opentype application/vnd.ms-fontobject image/svg+xml;
    gzip_vary on;
    gzip_comp_level  6;

    proxy_pass  http://app-5000;


    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_set_header Host $http_host;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header X-Forwarded-Port $server_port;
    proxy_set_header X-Request-Start $msec;
  }
  include /home/dokku/app/nginx.conf.d/*.conf;

  error_page 400 401 402 403 405 406 407 408 409 410 411 412 413 414 415 416 417 418 420 422 423 424 426 428 429 431 444 449 450 451 /400-error.html;
  location /400-error.html {
    root /var/lib/dokku/data/nginx-vhosts/dokku-errors;
    internal;
  }

  error_page 404 /404-error.html;
  location /404-error.html {
    root /var/lib/dokku/data/nginx-vhosts/dokku-errors;
    internal;
  }

  error_page 500 501 503 504 505 506 507 508 509 510 511 /500-error.html;
  location /500-error.html {
    root /var/lib/dokku/data/nginx-vhosts/dokku-errors;
    internal;
  }

  error_page 502 /502-error.html;
  location /502-error.html {
    root /var/lib/dokku/data/nginx-vhosts/dokku-errors;
    internal;
  }
}

upstream app-5000 {

  server 172.17.0.8:5000;
}

Answer 1

未转发原因短语的原因是由于nginx监听了http2。 Http2取消了http1.1的原因短语，而解决它的方法将是迫使nginx监听http1.1。

nginx.conf

...

server {
  listen      [::]:443 ssl;
  listen      443 ssl;

  server_name api.app.com; 
  access_log  /var/log/nginx/app-access.log;
  error_log   /var/log/nginx/app-error.log;

...

这将解决原因短语不被转发的问题。

Nginx不转发原因短语

1 个答案: