From: Alaa A. El F. <al...@tr...> - 2011-04-26 10:47:23
|
Try upgrading to 2.1.6 which we just released, it fixed the CSRF issue. cheers, Alaa On Tue, 26 Apr 2011 01:48:53 -0700 Cecilia Albertsson <cec...@lu...> wrote: > > Addendum: > > I was kindly pointed (thanks Chris!) to the thread on this list about > CSRF functionality of Django preventing accept/reject of suggestions, > but there is no file csrf.py on my system, so I don't see where to > edit what in order to solve the problem. Besides, since it's a > security fix, I guess it would not be recommended to make such an > edit..? Also, I understood that this security fix happens to be > included precisely in Django 1.1.4, and thus the Django update is > likely the source of my problems after all: > http://www.djangoproject.com/weblog/2011/feb/08/security/ > > Debugging with the WebKit web inspector I indeed get a csrf-related > error message: > > <html xmlns="http://www.w3.org/1999/xhtml" > xml:lang="en"><body><h1>403 Forbidden</h1><p>Cross Site Request > Forgery detected. Request aborted.</p></body></html> > > Any ideas anyone? > > Cecilia > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > Translate-pootle mailing list > Tra...@li... > https://lists.sourceforge.net/lists/listinfo/translate-pootle |