Hi, 
 I am developing a management system by django 1.6.  Using django + wsgi + 
apache to implement this project, there are some html on the one directory, 
angularjs $http use "POST" mehtod to visit the django web url to get some 
data (django web url on the other directory). 

front end angularjs code:
tagManControllers.controller('loginController', ['$scope', '$http', 
'$window', '$cookies',
    function($scope, $http, $window, $cookies){

        $scope.login = function(){

 
            //call the remote service
            var passwd_md5 = CryptoJS.MD5($scope.password);

            $http({method: 'GET', url: login_url + $scope.name + '&p=' + 
passwd_md5})
                .success(function(data, status, headers, config){

                    if (data.result == '200'){

                        var tmp_url = data.link;
                        $cookies.csrftoken = data.token; //get cookie from 
server
                        $window.location.href = tmp_url;
                    }
                    else{

                        $window.alert(tmp_info);
                    }

                })
                .error(function(data, status, headers, config){
   
                });
            return true;
        };
    }]);
 
backend python:
   result['token'] = request.META['CSRF_COOKIE']
    jsonReturn = json.dumps(result, indent=4)
    response = HttpResponse(jsonReturn, content_type="application/json", 
status=200)


"post" method frontend code:
     $scope.addTag = function(){

            var json_string = JSON.stringify($scope.tag_);
            var csrftoken = $cookies.csrftoken;

            $http({method:'POST', url: add_tags_url + json_string, 
headers:{'X-CSRFToken': csrftoken}})
                .success(function(data){

                    if(data.result != '200'){
                       
                        $window.alert(tmp_info);
                    }
                })
                .error(function(data){

                 
                });
        };

return error info:
Forbidden (403)

CSRF verification failed. Request aborted.
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<http://docs.djangoproject.com/en/dev/ref/contrib/csrf/#ref-contrib-csrf>
 has 
not been used correctly. For POST forms, you need to ensure:

   - Your browser is accepting cookies.
   - The view function uses 
RequestContext<http://docs.djangoproject.com/en/dev/ref/templates/api/#subclassing-context-requestcontext>
 for 
   the template, instead of Context.
   - 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.





-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/ec748562-4220-42d2-9448-f4f44cd09cfe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to