#34290 closed New feature (needsinfo)
X-Forwarded-Prefix support
Reported by: | Marc Perrin | Owned by: | nobody |
---|---|---|---|
Component: | HTTP handling | Version: | 4.1 |
Severity: | Normal | Keywords: | X-Forwarded |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
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?
Change History (2)
comment:1 by , 22 months ago
Resolution: | → needsinfo |
---|---|
Status: | new → closed |
comment:2 by , 22 months ago
Thanks for the answer, yeah it seems non-standard (Traefik reverse proxy; also mentioned here: https://microsoft.github.io/reverse-proxy/articles/transforms.html)
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.Is this standard at all? I couldn't find any RFC or reliable docs on this.
Please use one of support channels for support questions.