x-forwarded-port header value is incorrect
See original GitHub issueAll requests have an x-forwarded-port
header, but they have an incorrect value. A tunnel is always over HTTPS, so the port should be 443, but currently it is 80. This makes libraries like Symfony think the url is something like https://xxx.loca.lt:80/xxx
.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9
Top Results From Across the Web
HTTP headers and Classic Load Balancers
If the X-Forwarded-For request header is not included in the request, the load balancer creates one with the client IP address as the...
Read more >Error 400 when client sends X-Forwarded-For header
The "X-Forwarded-For" header is expected to just have an IP address with no port details. If do you see it, the port info...
Read more >X-Forwarded-For - HTTP - MDN Web Docs
The X-Forwarded-For header is untrustworthy when no trusted reverse proxy (e.g., a load balancer) is between the client and server. If the ...
Read more >HTTP header manipulation - Envoy Proxy
An invalid (not “http” or “https”) scheme, or an https scheme over an ... 2) From the value of the x-forwarded-proto header after...
Read more >Why are clients allowed to spoof the X-Forwarded-Port header?
At worst, the client is sending an incorrect X-Forwarded-Port value that doesn't match the port it actually connected to.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks @TheBoroer, works like a charm 😁
Whoohoo! I’ll go ahead and close this issue then! Thanks for opening & chiming in on this issue! Sorry it took a while for me to realize what was wrong 😅