ProxyHeadersMiddleware not using the X-Forwarded-Port header

[fiannac]

Discussed in #1948

^{Originally posted by fiannac April 21, 2023}
From the documentation:
--proxy-headers / --no-proxy-headers Enable/Disable X-Forwarded-Proto, X-Forwarded-For, X-Forwarded-Port to populate remote address info.

But I've noticed that, when the flag is set, the X-Forwarded-Port is not actually used by the application, and the source port is always set to 0.
This has to do with how the `ProxyHeadersMiddleware' is implemented, which does not match the behavior described in the docs.

Important

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.

[Kludex]

The discussion is already created.

[Kludex]

Is there any server implementation that uses X-Forwarded-Port?

[victor-torres]

@Kludex https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/x-forwarded-headers.html