Trying to upload a file to an instance running on Windows — or when baseurl is configured — results in errors and empty files. This issue stems from the tusPostHandler, which uses an absolute path for the Location header. Unfortunately, the tus-js-client library doens't handle absolute paths properly and causes the request url to have an additional slash:

http://localhost:8080/api/tus//example/file.jpg

While Linux handles that without issues, Windows returns an error:

404 127.0.0.1 lstat //example/file.jpg: file does not exist

Additionally, the baseurl configuration was being ignored, leading to further problems. The introduced changes will ensure that the upload url is now properly constructed and follows the expected format:

http://localhost:8080/baseurl/api/tus/example/file.jpg