> > also, please note that even if GET requests are mostly readonly, > if they return JSON, they can be still read by a CSRF attack, > so those have to be secured ( usually be verifying > the special header set by ajax requests ). > > gabor
That's more of a "JSON hijacking" attack than CSRF. It would be nice if there was a way for Django to automatically avoid this as well (maybe another middleware that does not allow returning a content type of 'application/json' if request.is_ajax() is false?), but that's a different issue entirely. -bob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
