在Google App Engine Flexible with Django上将http永久重定向到https

设置 secure 在应用程序yaml仅适用于GAE标准但不灵活。这个 app.yaml docs for Flexible 别提这把钥匙。

您可能需要在应用程序级别检查 X-Forwarded-Proto https here .

确保你有 SecurityMiddleware 和 CommonMiddleware 启用,并分配 Base_URL :

settings.py :

MIDDLEWARE_CLASSES = (
    ...
    'django.middleware.security.SecurityMiddleware'
    'django.middleware.common.CommonMiddleware',    
)

BASE_URL = 'https://www.example.com'

或者,您可以编写自己的中间件:

MIDDLEWARE_CLASSES = (
    ...
    'core.my_middleware.ForceHttps',
)

BASE_URL = 'https://www.example.com'

my_middleware.py :

from django.http import HttpResponsePermanentRedirect

class ForceHttps(object):

    def process_request(self, request):

        if not (request.META.get('HTTPS') == 'on' and settings. BASE_URL == 'https://' + request.META.get('HTTP_HOST') ):
            return HttpResponsePermanentRedirect(settings. BASE_URL + request.META.get('PATH_INFO'))
        else:
            return None

问题是标题名。当通过WSGI服务器访问Django时,应该使用 X-Forwarded-Proto 标题而不是 HTTP_X_FORWARDED_PROTO .

见: Why does django ignore HTTP_X_FORWARDED_PROTO from the wire but not in tests?

经过反复试验,我发现设置.py将允许的主机更新到适当的域会得到所需的结果:

ALLOWED_HOSTS = ['https://{your-project-name}.appspot.com','https://www.yourcustomdomain.com'] 

更新:我不再确定上述原因,因为在随后的部署中,上述内容被拒绝,我收到了主机错误。然而,重定向仍然存在。。。:(