错误 Bad Request (400),当我访问域上的站点时
Posted
技术标签:
【中文标题】错误 Bad Request (400),当我访问域上的站点时【英文标题】:error Bad Request (400), when I go to the site on the domain 【发布时间】:2018-07-27 09:32:03 【问题描述】:我在 digitalocean.com 上启动了 django 项目。问题是在我的 IP 地址上加载了我的网站并且没有问题,但是如果我通过域,“错误请求错误(400)”。在 godaddy.com 购买的域名。域名设置正确按照托管教程https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars:
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com
配置 nginx:
upstream bbb_app_server
# 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:/webapps/bbb/run/gunicorn.sock fail_timeout=0;
server
listen 80;
server_name example.ru;
client_max_body_size 4G;
access_log /webapps/bbb/logs/nginx-access.log;
error_log /webapps/bbb/logs/nginx-error.log;
location /static/
alias /webapps/bbb/static/;
location /media/
alias /webapps/bbb/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://bbb_app_server;
break;
# Error pages
error_page 500 502 503 504 /500.html;
location = /500.html
root /webapps/bbb/static/;
这是我对 settings.py 的设置:
try:
from .settings_prod import *
except:
pass
这是我对 settings_prod.py 的设置:
DEBUG = False
ALLOWED_HOSTS = ['0.80.00.000',
'.example.ru']
DATABASES =
'default':
'ENGINE': 'django.db.backends.postgresql_psycopg2',
'NAME': 'db1',
'USER': 'bbb',
'PASSWORD': 'bbb',
'HOST': 'localhost',
'PORT': '',
检查了 nginx -t:
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
【问题讨论】:
如果直接输入digitalocean ip就可以了? 是的,它在 ip address digitalocean.com 上运行良好 可以分享你的ip和域名吗?看起来记录不匹配 你检查 nginx 访问和错误日志了吗? nginx:配置文件/etc/nginx/nginx.conf语法没问题 nginx:配置文件/etc/nginx/nginx.conf测试成功 【参考方案1】:您处理设置的方式似乎是问题所在。
如果我理解正确,您有一个 settings.py 和一个 settings_prod.py。
然后,在 settings.py 中,您将从 settings_prod.py 导入所有信息。
我认为正在发生的是,这个导入发生在文件的顶部。然后,可能在 settings.py 的其余部分中,您可能有另一个 ALLOWED_HOSTS
,它会覆盖您在 settings_prod.py 中定义的 ALLOWED_HOSTS = ['0.80.00.000', '.example.ru']
。。 p>
如果移动以下代码:
try:
from .settings_prod import *
except:
pass
到settings.py文件的底部,它将正确覆盖配置。
【讨论】:
是的,您对 settings.py 和 settings_prod.py 的理解正确。但是try: from .settings_prod import * except: pass
在文件settings.py的底部
暂时将DEBUG
更改为True
,重新启动 Gunicorn 进程并访问该页面,看看您遇到了什么错误。或者,如果您已正确配置日志记录,请检查 Gunicorn 的日志。
最后,我按照settings.py中的设置更改了设置并重新启动。以上是关于错误 Bad Request (400),当我访问域上的站点时的主要内容,如果未能解决你的问题,请参考以下文章
nginx:400 Bad RequestThe plain HTTP request
Retrofit 2.0 - 如何获取 400 Bad Request 错误的响应正文?
Java访问.net的webservice,访问客户给的可以,但是访问免费的不行出现错误(400)Bad Request。要怎么解决
[linux] FastDFS访问文件,400 Bad Request