#23585: Fix misleading comment in CSRF middleware
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: aaugustin
Type: | Status: closed
Cleanup/optimization | Version: master
Component: contrib.csrf | Resolution: fixed
Severity: Normal | Triage Stage: Ready for
Keywords: | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Grzegorz Slusarek <grzegorz.slusarek@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"b4bb5cd0a31c6e9ebc2be9dff245f506940f9159"]:
{{{
#!CommitTicketReference repository=""
revision="b4bb5cd0a31c6e9ebc2be9dff245f506940f9159"
Fixed #23585 - Corrected internal comment.
Removed misleading comment and provide correct one, explaining
idea behind hardcoded CSRF template context processor.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23585#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.f186601ff3a6029dcac39bd5960c0a7d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
