Re: Forbidden (CSRF token missing or incorrect.)

when using the development server over HTTP, don't set these values:

    CSRF_COOKIE_SECURE = True

    SESSION_COOKIE_SECURE = True

On Wednesday, November 21, 2018 at 5:38:19 AM UTC-8, Rabah Saadi wrote:

Hello,

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/7efcc063-c238-4cba-8254-00b2dfecbcba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.