使用apache+mod_wsgi方式部署完成后，访问网站时400(Bad Request)

这是个血淋淋的教训，浪费青春的举动。

        这几天使用linux+apache部署了一个生产环境用的网站环境，用到了django框架，在django的官网和其余网站上找到了不少部署的方法，其中wsgi方式其中比较方便和快速入手的一种。

        在全部工做部署工做完成后，经过域名访问网站，发现提示：400（Bad Request）。

        网上搜了n多文章，浪费了几个小时的时间去查找错误，未果。

        无奈。。。。，继续奋斗。。。。search、search、google

        苦尽甘来，通过一番折腾，终于发现了一篇文章，http://stackoverflow.com/questions/20321673/debugging-apache-django-wsgi-bad-request-400-error （这是谢谢这哥们了，心情无以附加，无以言表）

        其实，缘由很简单，就是在将django投入生产环境后：settings.py里的配置要作相应的修改

#一下几项需更改
DEBUG = False      # 由True到False，这个我也作对了

# 下面这个，忘记了，高了半天，废了老大劲才知道是这的问题
ALLOWED_HOSTS = [
    '.example.com', # Allow domain and subdomains
    'localhost', # Also allow FQDN and subdomains]

        问题解决，检讨。。。

        到这里我才恍悟，记得在django的官方文档中是有的啊，

        附上官网的说明，

        首先：

Host header validation

Django uses the Host header provided by the client to construct URLs in certain cases. While these values are sanitized to prevent Cross Site Scripting attacks, a fake Host value can be used for Cross-Site Request Forgery, cache poisoning attacks, and poisoning links in emails.

Because even seemingly-secure web server configurations are susceptible to fake Host headers, Django validates Hostheaders against the ALLOWED_HOSTS setting in the django.http.HttpRequest.get_host() method.

This validation only applies via get_host(); if your code accesses the Host header directly from request.META you are bypassing this security protection.

For more details see the full ALLOWED_HOSTS documentation.

Warning

Previous versions of this document recommended configuring your web server to ensure it validates incoming HTTP Host headers. While this is still recommended, in many common web servers a configuration that seems to validate the Host header may not in fact do so. For instance, even if Apache is configured such that your Django site is served from a non-default virtual host with the ServerName set, it is still possible for an HTTP request to match this virtual host and supply a fake Host header. Thus, Django now requires that you set ALLOWED_HOSTSexplicitly rather than relying on web server configuration.

Additionally, as of 1.3.1, Django requires you to explicitly enable support for the X-Forwarded-Host header (via theUSE_X_FORWARDED_HOST setting) if your configuration requires it.

url：https://docs.djangoproject.com/en/1.6/topics/security/

其次：

ALLOWED_HOSTS

Default: [] (Empty list)

A list of strings representing the host/domain names that this Django site can serve. This is a security measure to prevent an attacker from poisoning caches and password reset emails with links to malicious hosts by submitting requests with a fake HTTP Host header, which is possible even under many seemingly-safe web server configurations.

Values in this list can be fully qualified names (e.g. 'www.example.com'), in which case they will be matched against the request’sHost header exactly (case-insensitive, not including port). A value beginning with a period can be used as a subdomain wildcard: '.example.com' will match example.com, www.example.com, and any other subdomain of example.com. A value of '*' will match anything; in this case you are responsible to provide your own validation of the Host header (perhaps in a middleware; if so this middleware must be listed first in MIDDLEWARE_CLASSES).

Note

If you want to also allow the fully qualified domain name (FQDN), which some browsers can send in the Host header, you must explicitly add another ALLOWED_HOSTS entry that includes a trailing period. This entry can also be a subdomain wildcard:

ALLOWED_HOSTS = [
    '.example.com', # Allow domain and subdomains
    '.example.com.', # Also allow FQDN and subdomains]

If the Host header (or X-Forwarded-Host if USE_X_FORWARDED_HOST is enabled) does not match any value in this list, thedjango.http.HttpRequest.get_host() method will raise SuspiciousOperation.

When DEBUG is True or when running tests, host validation is disabled; any host will be accepted. Thus it’s usually only necessary to set it in production.

This validation only applies via get_host(); if your code accesses the Host header directly from request.META you are bypassing this security protection.

url：https://docs.djangoproject.com/en/1.6/ref/settings/#std:setting-ALLOWED_HOSTS

最后，生命很宝贵，请不要浪费。

谨记：每每出错的地方就是在她最根本的地方，回归本源，才能看清事物的原貌。