Forbidden (403) CSRF verification failed. Request aborted.

Forbidden (403)
CSRF verification failed. Request aborted.
You is seeing this message because this site requires a CSRF cookie when submitting forms. This cookie was required for security reasons, to ensure that your browser was not being hijacked by third parties.
If you had 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 are a genuine cross Site Request forgery, or when Django ' s CSRF mechanism have not bee n 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 are a {% Csrf_token%} template tag inside each POST form that targets an internal URL.
If you is not using the Csrfviewmiddleware and then you must use Csrf_protect on any of the Csrf_token template tag, As well as those that accept the POST data.
You ' re seeing the "Help" section of the "This" page because you has DEBUG = True in your Django settings file. Change so to False, and only the initial error message would be displayed.
You can customize this page using the Csrf_failure_view setting.

been tossing for a long time, the final solution is to refer to the http://blog.csdn.net/middlekingt/article/details/8593031 inside add a decorator good.

But the problem remained, and later saw another way on this site: o Manually exclude a view function fromBeing handled by either of the and the Csrfmiddleware, you can use the Csrf_exempt decorator, foundinchTHEDJANGO.VIEWS.DECORATORS.CSRF module. For example: fromdjango.views.decorators.csrf Import csrf_exempt@csrf_exemptdef my_view (Request):returnHttpResponse ('Hello World'Like the middleware, the csrf_exempt decorator isComposed of 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 used individually ifrequired finally solved the problem. I actually bypassed the problem because Django introduced CSRF to avoid the cross Site Request forgeries attack, and the above workaround just forbids the Django feature. So in the future we have to study carefully, in the premise of this function can not help to submit a successful form. 

Forbidden (403) CSRF verification failed. Request aborted.