#34290: X-Forwarded-Prefix support
-----------------------------------------+-----------------------------
Reporter: Marc Perrin | Owner: nobody
Type: New feature | Status: new
Component: HTTP handling | Version: 4.1
Severity: Normal | Keywords: X-Forwarded
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+-----------------------------
Is there any plan to deal with the **X-Forwarded-Prefix** header?
(similar to
{{{
USE_X_FORWARDED_HOST
}}}
and
{{{
USE_X_FORWARDED_PORT
}}}
for X-Forwarded-Host and X-Forwarded-Port)
(NB: and as far as X-Forwarded-Proto is concerned, it's usually dealt with
via
{{{
SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
}}}
)
Or is this header not standard enough?
If not, what would be a standard - or at least effective - way for a user
to (sort of) customize HttpRequest (get_raw_uri, build_absolute_uri) to
deal with this header?
--
Ticket URL: <https://code.djangoproject.com/ticket/34290>
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/01070185e5d8c65f-09fb700e-e0a2-45f8-a65d-c910a0aac5c6-000000%40eu-central-1.amazonses.com.
