#30732: The default SameSite cookie flag breaks xframe_options_exempt
-------------------------------------+-------------------------------------
Reporter: Dan Braghis | Owner: Jezeniel
Type: | Zapanta
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 2.2
Severity: Normal | Resolution:
Keywords: CSRF, SameSite, | Triage Stage: Accepted
Clickjacking |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jezeniel Zapanta):
Replying to [comment:2 Carlton Gibson]:
> These topics are orthogonal, but, OK yes, often the reason to allow use
in an iframe would be form submission.
>
> As such, a note in `docs/ref/clickjacking.txt` cross-linking to the
`CSRF_COOKIE_SAMESITE` and/or `SESSION_COOKIE_SAMESITE` docs would seem
appropriate.
I have some questions regarding this, maybe this is somehow unrelated to
the ticket but what if you just want to disable the `CSRF_COOKIE_SAMESITE`
to a certain view? If we modify `CSRF_COOKIE_SAMESITE` it will be disabled
globally, what if you want granular control over this? Will it be possibe?
Will this also be possible?
--
Ticket URL: <https://code.djangoproject.com/ticket/30732#comment:4>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.9e759ac71cf0e35a42a5a0b06937652e%40djangoproject.com.
