Support configurable timeoutInterval for upload requests (parity with Android client)

[sarikavijayan]

In the current implementation of TUSKit (iOS), URLRequest timeout is hardcoded to 30 seconds in TUSAPI.swift:

URLRequest(url: url, cachePolicy: .reloadIgnoringLocalAndRemoteCacheData, timeoutInterval: 30)

This approach limits flexibility when dealing with large file uploads or slow networks, and does not allow developers to control how long a request can take before timing out.

Comparison with Android TUS Client:
The Android Tus client provides timeout configurability through the following API:

TusClient().connectTimeout(...)

This allows developers to easily adjust request behavior to suit various conditions and use cases.

Feature Request:

Add support for a configurable timeoutInterval for upload requests in TUSKit , ideally exposed via TUSClient property, so developers can set this globally.

[donnywals]

This approach limits flexibility when dealing with large file uploads or slow networks, and does not allow developers to control how long a request can take before timing out.

The timeoutinterval does not interfere with the ability to upload large files, iOS only uses that interval to control how long the request should wait for a server connection as explained here: https://developer.apple.com/documentation/foundation/nsurlrequest/timeoutinterval

If during a connection attempt the request remains idle for longer than the timeout interval, the request is considered to have timed out.

I'm not necessarily opposed to making this a configurable property, but I'm not exactly certain that there's any real benefit to this given that we're not currently experiencing issues related to timeouts that I'm aware of. If this request was prompted from experiencing an issue I'd love some more context about the experience you've had

[sarikavijayan]

@donnywals

I'm currently using TUSKit to upload large media files. In our use case, each chunk is relatively large due to specific application requirements (e.g., minimizing the number of requests). However, during this process we are experiencing a high volume of HTTP 502 (Bad Gateway) errors from the server, especially under slower network conditions.

After reviewing the source, I noticed that URLRequest in TUSAPI.makeRequest(...) uses a hardcoded timeout of 30 seconds:

While I understand that timeoutInterval only affects connection and idle timeout behavior (and not the total upload time), this still becomes significant when dealing with large chunks that may take longer to initiate or transfer over unreliable networks.

[donnywals]

I will consider allowing to configure this timeout.

That said, a 502 HTTP status code usually means that there's something happening on the server rather than the app side. So even with an increased timeout on the app side, it seems unlikely that this would resolve your problem.

As a proof of concept, you could create a form of TUSKit and increase the timeout. If that solves your problems, I will happily accept a PR that has an increased timeout (or that implements a configurable timeout).

That said, a 502 is more likely a server side issue related to a proxy or CDN