#19517: Add support for X-Forwarded-Port to HttpRequest.get_host when
USE_X_FORWARDED_HOST is in use
-------------------------------------+-------------------------------------
Reporter: david_k_hess@… | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: 1.4
Severity: Normal | Resolution: wontfix
Keywords: httprequest, | Triage Stage: Accepted
get_host, X-Forwarded-Host, | Needs documentation: 0
USE_X_FORWARDED_HOST | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by collinanderson):
There's a new `Forwarded:` header that standardizes `for`, `proto`,
`host`, and `by`, but not `port`. http://tools.ietf.org/html/rfc7239
If you want to discuss it further, please use the
https://groups.google.com/d/forum/django-developers mailing list, as this
is a closed ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/19517#comment:8>
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/078.3cc78082e0677accde8ee8735d415043%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.