Switch from HTTPS to HTTP Causes Mixed Content Errors

[angelorc]

Describe the bug
When initiating an upload over HTTPS, the tus-js-client library seems to switch the protocol to HTTP, which leads to mixed-content errors on browsers. This subsequently prevents the file from being uploaded successfully.

To Reproduce
You can try using this temporary url https://testnet-bstudio-go-ui.fly.dev/settings/profile

Expected behavior
The tus-js-client library should maintain the protocol (HTTPS) as specified during the initiation of the upload and not switch to HTTP, thereby preventing mixed content errors.

[angelorc]

Well, the issue was on our backend, for some reason it change the location header. We fixed it by forcing our backend to keep https