Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix CSRF when CSRF_USE_SESSIONS is enabled #619

Merged
merged 2 commits into from
May 22, 2024
Merged

Fix CSRF when CSRF_USE_SESSIONS is enabled #619

merged 2 commits into from
May 22, 2024

Commits on May 15, 2024

  1. Fix CSRF when CSRF_USE_SESSIONS is enabled 

    The front-end currently checks for the
`input[name="csrfmiddlewaretoken"]` element if `CSRF_COOKIE_HTTPONLY` is
set, but according to the [Django docs], it should do the same thing if
`CSRF_USE_SESSIONS` is set, as it will also mean the token is not
available in a cookie.

[Django docs]: https://docs.djangoproject.com/en/5.0/howto/csrf/#acquiring-the-token-if-csrf-use-sessions-or-csrf-cookie-httponly-is-true
    @cpmsmith
    cpmsmith committed May 15, 2024
    Configuration menu
    Copy the full SHA
    88b571c View commit details
    Browse the repository at this point in the history

Commits on May 16, 2024

  1. Merge branch 'master' into csrf-use-sessions

    @chrisclark
    chrisclark authored May 16, 2024
    Configuration menu
    Copy the full SHA
    fdfc9e8 View commit details
    Browse the repository at this point in the history