#34953: CSRF verification fails even with CSRF middleware commented out
------------------------------+--------------------------------------
Reporter: Fabio Araujo | Owner: nobody
Type: Bug | Status: closed
Component: CSRF | 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 Natalia Bidart):
* status: new => closed
* resolution: => invalid
Comment:
Hello Fabio, thank you for taking the time to create a ticket.
From your description, it seems that the problem may be a configuration
issue or something specific of your project. This report seems better
suited to be a support request: the best place to get answers to your
issue is using any of the user support channels from
[https://docs.djangoproject.com/en/dev/faq/help/#how-do-i-do-x-why-
doesn-t-y-work-where-can-i-go-to-get-help this link].
Since the goal of this issue tracker is to track issues about Django
itself, and your issue seems, at first, to be located in your custom code,
I'll be closing this ticket as invalid. If, after debugging, you find out
that this is indeed a bug in Django, please re-open with the specific
details and please be sure to include a small Django project to reproduce
or a failing test case.
--
Ticket URL: <https://code.djangoproject.com/ticket/34953#comment:1>
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/0107018baaf5b579-50735432-4821-4406-b95d-91f2d2a7aa00-000000%40eu-central-1.amazonses.com.
