#26094: CSRF fails behind proxy (settings.USE_X_FORWARDED_PORT=True)
---------------------------------+------------------------------------
Reporter: chemary | Owner: nobody
Type: Bug | Status: closed
Component: CSRF | Version: 1.9
Severity: Release blocker | Resolution: fixed
Keywords: csrf | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"076d4591108764695582ab272fdb7f348b4c161c" 076d459]:
{{{
#!CommitTicketReference repository=""
revision="076d4591108764695582ab272fdb7f348b4c161c"
[1.9.x] Fixed #26094 -- Fixed CSRF behind a proxy
(settings.USE_X_FORWARDED_PORT=True).
Backport of 2d28144c9519f4e4397c70f045c2b1d31437bf69 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26094#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 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/065.df60a25ef78158f68181af6b279269c0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
