#34290: X-Forwarded-Prefix support
-------------------------------+--------------------------------------
Reporter: Marc Perrin | Owner: nobody
Type: New feature | Status: closed
Component: HTTP handling | Version: 4.1
Severity: Normal | Resolution: needsinfo
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
-------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => needsinfo
Comment:
Thanks for the ticket. TBH, I've never heard about `X-Forwarded-Prefix` it
seems to be another non-standard header set by some proxies.
> Or is this header not standard enough?
Is this standard at all? I couldn't find any RFC or reliable docs on this.
> 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?
Please use one of
[https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
support channels] for support questions.
--
Ticket URL: <https://code.djangoproject.com/ticket/34290#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/01070185e748c71a-5ff018eb-1008-4605-bb26-160a47806e26-000000%40eu-central-1.amazonses.com.
