Thursday, August 27, 2020

Authenticate user stalls on 302 after POST is successful

Hello,

SUMMARY:
During user authentication, POST is successful but will stall on the 302 redirect.

INFO:
On Chrome(85.0.4183.83)
Django 2.1 & Django 3.1
DEBUG = True, 
Happens rarely on HTTPS live-servers

STEPS TO REPRODUCE:
  1. On chrome browser, run manage.py runserver
  2. Using a custom AUTH_USER_MODEL, authenticate a user
  3. Local machine will return "POST / HTTP/1.1" 302 0 and stall here
  4. Refreshing page will return GET 200
  5. All following authentication/redirects will work normally

WHAT I'VE TRIED:
Set CSRF_COOKIE_SAMESITE = 'Strict' as indicated by Stack overflow
Cleared Cookies before-hand
Works on Microsoft Edge(84.0.522.63)
Does not happen on live servers launched 

RESOURCE:
https://bugs.chromium.org/p/chromium/issues/detail?id=1099122

QUESTIONS:
Has anyone else encountered this issue?
Has anyone else found a solution that works?



--
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 view this discussion on the web visit https://groups.google.com/d/msgid/django-users/af5bbd03-7349-428b-b9cb-d76505095623n%40googlegroups.com.

No comments:

Post a Comment