django 오류 - Reason given for failure: CSRF cookie not set.

{% csrf_token %} 
     

This should not be done for POST forms that target external URLs, sincethat would cause the CSRF token to be leaked, leading to a vulnerability.

In the corresponding view functions, ensure that the'django.core.context_processors.csrf' context processor isbeing used. Usually, this can be done in one of two ways:

1. Use RequestContext, which always uses'django.core.context_processors.csrf' (no matter what yourTEMPLATE_CONTEXT_PROCESSORS setting). If you are usinggeneric views or contrib apps, you are covered already, since theseapps use RequestContext throughout.

2. Manually import and use the processor to generate the CSRF token andadd it to the template context. e.g.:

   from django.core.context_processors import csrf
   from django.shortcuts import render_to_response
   
   def my_view(request):
       c = {}
       c.update(csrf(request))
       # ... view code here
       return render_to_response("a_template.html", c)
   

   
   You may want to write your own render_to_response wrapper thattakes care of this step for you.


The utility script extras/csrf_migration_helper.py can help to automate thefinding of code and templates that may need to be upgraded. It contains fullhelp on how to use it.
그러나 문제는 여전하다. 나중에 또 다른 방식이 이 사이트에 있다.
o manually exclude a view function from being handled by either of the two CSRFmiddleware, you can use the csrf_exempt decorator, found in thedjango.views.decorators.csrf module. For example:

from django.views.decorators.csrf import csrf_exempt

@csrf_exempt
def my_view(request):
    return HttpResponse('Hello world')


Like the middleware, the csrf_exempt decorator is composed of two parts: acsrf_view_exempt decorator and a csrf_response_exempt decorator, foundin the same module. These disable the view protection mechanism(CsrfViewMiddleware) and the response post-processing(CsrfResponseMiddleware) respectively. They can be used individually ifrequired.
마침내 이 문제를 해결했다.
사실 나는 이 문제를 돌렸다. 왜냐하면django가 CSRF를 도입한 것은 크로스 시트 Request Forgeries 공격을 피하기 위해서였고, 위의 해결 방법은 이django의 기능을 마침 금지했기 때문이다.그래서 앞으로 꼼꼼히 연구해 이 기능을 잃지 않는 전제에서 표를 성공적으로 제출해야 한다.
끝나다
다음으로 이동:http://blog.csdn.net/huangxiansheng1980/article/details/7482591