Location header set to http when deployed behind reverse proxy
psmirnov-dermview opened this issue · comments
Describe the bug
TUS Server in Laravel listening on http port 80, deployed behind https proxy, e.g. AWS ELB.
Responses sent by TUS Server contain http://..../ which breaks the frontend library, as actual location is https://.../
To Reproduce
Steps to reproduce the behavior:
- Deploy behind https enabled proxy
- Try uploading files
- POST requests will succeed but contain invalid http:// Location, subsequent requests will fail.
Expected behavior
To be compatible with a range of proxy configurations Location header should not really have the $scheme://$host:$port
Instead it should be a relative link unless ApiPath was configured using FQDN.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.
Closing because of inactivity.