@stefanbenten commented on GitHub:
transfer.sh is currently running with nginx in front and the correct proxy pass directive added. That said, it has a timeout at 1800s per request, due to the…
@stefanbenten commented on GitHub:
I think i have an idea why it is not working correctly. Lemme debug the code (because the proxy forwards it correctly) and put up a PR.
@paolafrancesca commented on GitHub:
HEAD requests do not return Accept-Ranges: bytes, I will fix that, as well of allowing partial download for every file type
this is related to the…
@paolafrancesca commented on GitHub:
indeed it's a rather tricky: we have a mutex on checkMetadata (35e794220b/serve…
@paolafrancesca commented on GitHub:
@ErrorNoInternet did you hit this issue with transfer.sh, intended as software, or on https://transfer.sh website?
can you tell me one of the parallel…
@paolafrancesca commented on GitHub:
@ErrorNoInternet here: https://github.com/dutchcoders/transfer.sh/pull/495
@ErrorNoInternet commented on GitHub:
@aspacca
did you hit this issue with transfer.sh, intended as software, or on https://transfer.sh/ website?
The https://transfer.sh website
can…
@paolafrancesca commented on GitHub:
@niss88 allowing parallel range request showed to be more complicated than I initially thought, especially regarding performance impact.
I will reserve to…
@robertgendler commented on GitHub:
Thanks for bringing this to our attention.
@robertgendler commented on GitHub:
Should be fixed. Thanks for bringing this to our attention.