django1.21加入了防止CSRF攻击的模块。
这是django的debug模式下给出的错误提示页面。
Forbidden (403)
CSRF verification failed. Request aborted.
Help
Reason given for failure:
CSRF token missing or incorrect.
In general, this can occur when there is a genuine Cross Site Request Forgery, or when Django's CSRF mechanism has not been used correctly. For POST forms, you need to ensure:
- The view function uses
RequestContextfor the template, instead ofContext. - In the template, there is a
{% csrf_token %}template tag inside each POST form that targets an internal URL. - If you are not using
CsrfViewMiddleware, then you must usecsrf_protecton any views that use thecsrf_tokentemplate tag, as well as those that accept the POST data.
You're seeing the help section of this page because you have DEBUG = True in your Django settings file. Change that to False , and only the initial error message will be displayed.
You can customize this page using the CSRF_FAILURE_VIEW setting.
在用户用POST方法提交页面信息的时候,有时会遇到这样的错误。在网上找了一些解决方案,其中比较方便的一个是在settings.py里面的MIDDLEWARE_CLASSES 中加入'django.middleware.csrf.CsrfResponseMiddleware', 错误就消除了。
本文介绍了在Django 1.21中如何通过CsrfViewMiddleware等组件来避免CSRF攻击,确保POST请求的安全性。
1664

被折叠的 条评论
为什么被折叠?



