Re: [Django] #34872: DRF Auth Issue

[Django]

#34872: DRF Auth Issue
---+--
 Reporter:  msillz |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  4.2
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => invalid
 * component:  CSRF => Uncategorized


Comment:

 This isn't the bug tracker for DRF, and you've make a support request
 rather than reported a bug. See TicketClosingReasons/UseSupportChannels
 for ways to get help.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018acf164751-e9698d58-3ce1-4175-8cba-93c9d011bd6d-00%40eu-central-1.amazonses.com.

[Django] #34872: DRF Auth Issue

[Django]

#34872: DRF Auth Issue
--+
   Reporter:  msillz  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  CSRF|Version:  4.2
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 Basic HTTP Authentication being listen above Session / Token
 authentication was causing some users to get "stuck". The template views
 were returning the current user's data however, the tokens from the DRF
 were still linked to a previous login.

 I don't know if this is my fault or not. That said, moving
 rest_framework.authentication.BasicAuthentication to the bottom fixed the
 issue. This seems like a design problem to me.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ace4aada0-0648ec41-b5e5-4f3e-992a-2c67ec4a6337-00%40eu-central-1.amazonses.com.