I had this error when I had two Django application with the same domain and
both with the same (default) CSRF cookie name. Changing the cookie name to
something different solved the issue.
On 30 May 2015 22:30, "Michael Greer" <mich...@tapptv.com> wrote:
> We have started seeing this behavior occasionally. No code change in this
> area, but sometimes (esp on phones) the CSRF cookie is wrong.
>
> Our guess is too many cookies on the domain, but it is difficult to prove
> this. Indeed, opening a new browser session resolves it... temporarily.
>
> -Mike
>
> On Tuesday, January 6, 2015 at 3:09:46 AM UTC-6, Sugita Shinsuke wrote:
>>
>> Hello.
>>
>> When I use Django via my smart phone Android and iOS.
>> The error sometimes occurred.
>>
>> Forbidden (403)
>> CSRF verification failed. Request aborted.
>> Help
>> Reason given for failure:
>> CSRF token missing or incorrect.
>>
>> In general, this can occur when there is a genuine Cross Site Request
>> Forgery, or when Django's CSRF mechanism has not been used correctly. For
>> POST forms, you need to ensure:
>> Your browser is accepting cookies.
>> The view function uses 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.
>>
>> I append django.middleware.csrf.CsrfViewMiddleware', of
>> MIDDLEWARE_CLASSES in settings.py
>>
>> I use
>> Python 2.7.5
>> Django 1.6.4
>>
>> Anyone who know this matter, please help.
>>
>> --
> 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/89d20584-d3bf-4104-b642-0f519c4deb10%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/89d20584-d3bf-4104-b642-0f519c4deb10%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
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/CACczBULNhCDS_w4YvaUb%2Byn0MjEosq6sR6TvmSSYJ7XbxCDHDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
