Django CSRF cookie not set.错误

post提交表单报错：

 

Forbidden (403)

CSRF verification failed. Request aborted.

You are seeing this message because this site requires a CSRF cookie when submitting forms. This cookie is required for security reasons, to ensure that your browser is not being hijacked by third parties.

If you have configured your browser to disable cookies, please re-enable them, at least for this site, or for 'same-origin' requests.

Help

Reason given for failure:

    CSRF cookie not set.
    

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:

• Your browser is accepting cookies.
• The view function passes a request to the template's render method.
• 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 use csrf_protect on any views that use the csrf_token template 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.

 

 

解决方法如下红色代码：

# coding:utf-8
from django.shortcuts import render_to_response
from blog.models import Blog
from django.http import HttpResponse
from django.views.decorators.csrf import csrf_exempt  

def index(request):
 blog_list=Blog.objects.all() #Blog.objects.all()获取Blog表中所有数据，并赋值给blog_list
 return render_to_response('index.html',{'blogs':blog_list}) #返回给浏览器一个index.html页面，并且将blog_list变量的值也返回给index.html

@csrf_exempt
def login(request):
 username=request.POST.get('username','')
 password=request.POST.get('password','')
if username == 'chen' and password == '123456':
return HttpResponse('login success!')
else:
return render_to_response('index.html',{'error':'username or password error!'})

转载于:https://www.cnblogs.com/wnfindbug/p/5585267.html