Re: Forbidden (CSRF token missing or incorrect.)

Hi Rabah,

I encountered a similar problem today and could pin it to the setting
"CSRF_COOKIE_SECURE = True". I don't use https on my development
machines so the cookie is not set. Changing the value to
"CSRF_COOKIE_SECURE = False" in my local settings solved it.

You may check, how you access your sites, by http or https.

Greetings,
Andreas

>> I've been using Django 2.2Dev for a while now, since April 2018, and it is
>> working just fine (I got my reasons why Django Dev). But since the last git
>> pull, it shows the CSRF token missing, on every page has a form with CSRF
>> token.
>>
>> Is there something broke or ... ? since My Django-2.2Dev before the last
>> "git pull" was working just fine.
>>
>> PS : Donwgrade to Django 2.1.3 stable, works fine too.
>>
>> thank you.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5f1fb893-a4e1-c74d-b11e-b8ec06ef892d%40kurs-10.de.
For more options, visit https://groups.google.com/d/optout.