#27958: CSRF_COOKIE reset while requesting a broken relative URL over HTTPS
-------------------------------------+-------------------------------------
Reporter: cryptogun | Owner: nobody
Type: Bug | Status: closed
Component: CSRF | Version: 1.10
Severity: Normal | Resolution: invalid
Keywords: csrf reset https | Triage Stage:
403 | 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
Comment:
If disabling `CSRF_COOKIE_HTTPONLY` fixes the issue, that should be fine
-- it offers little practical security, see #27611. If you want to keep it
enabled, then you need to submit AJAX requests as described in #27534.
Next time, you might want to ask on our
[TicketClosingReasons/UseSupportChannels support channels] unless you are
really sure the issue is a bug. As far as I can tell, there's no issue
here. Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/27958#comment:3>
Django <https://code.djangoproject.com/>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.8df7efd08b39a4443d7470a0d72853d8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
