7 months ago
Frameworks often require to configure a trusted proxy when the application runs behind a load balancer. In my case it is Laravel. I spent quite some time to figure out what the issue with my signed URLs is and to fix it for Railway.
If the header X-FORWARDED-PORT was automatically set by Railway, similar to X-FORWARDED-PROTO and X-FORWARDED-HOST, it would simply work out of the box. As it is not, you need to put some custom hard-coded workarounds into the codebase.
I think this would be a simple fix to improve developer experience 
0 Threads mention this feature
2 Replies
a month ago
Any movement or possibilities for this? I'm just running up against this with my application, fwiw @raphaelflash, do you have any references about the hard-coded methods to get this working with workarounds?
becurrie
Any movement or possibilities for this? I'm just running up against this with my application, fwiw @raphaelflash, do you have any references about the hard-coded methods to get this working with workarounds?
a month ago
hi @becurrie, this did the trick for me: https://gist.github.com/raphaelflash/67024178add740ef517549a914de8225