You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, i am not using the resumable uploads because of this bug.
When my users trying to upload a file for more then 10+- minutes, they are getting an error with status 404. for me it seems like timeout error.
I tried to adjust the req.setTimeout function in the express, but unfortunately with no success. i did change the timeout but it has limitation so i thought it might be a client side timeout, but i cannot change the client side timeout because it is not possible with tus-js-client
Steps to reproduce the behavior:
Use tus-js-client, tus/server and tus/gcs-store
Start upload, use Slow 3G internet upload speed (or lower) to mock a very slow upload
See error after 10.9 minutes
More about the error:
Request timings:
Request details:
*notice that Keep-Alive:timeout=5 has no role here though its return from the BE side (witch the timeout is controlled properly there.. i guess)
Setup details
Please provide following details, if applicable to your situation:
Yes! upgrade version solve the problem. wasn't that easy to upgrade it though. i can see that the upload protocol works differently (better!)
FYI: onResponseError does not catching every error from some readon...
thanks alot !! @fenos
First, i am not using the resumable uploads because of this bug.
When my users trying to upload a file for more then 10+- minutes, they are getting an error with status 404. for me it seems like timeout error.
I tried to adjust the
req.setTimeout
function in the express, but unfortunately with no success. i did change the timeout but it has limitation so i thought it might be a client side timeout, but i cannot change the client side timeout because it is not possible with tus-js-clientSteps to reproduce the behavior:
More about the error:
Request timings:
Request details:
*notice that
Keep-Alive:timeout=5
has no role here though its return from the BE side (witch the timeout is controlled properly there.. i guess)Setup details
Please provide following details, if applicable to your situation:
The text was updated successfully, but these errors were encountered: