Network Timeout on (Relatively) Large Files

[W1BTR]

Operating system

Windows

Joplin version

3.2.13

Desktop version info

Joplin 3.2.13 (prod, win32)

Client ID: a77b426142df4a2b8eb962de58083656
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: a898e17

Backstage: 1.0.0
Backup: 1.4.2
Better Code Blocks: 2.0.0
Bible Quote: 2.1.0
Code-Clipboard: 1.0.0
Conflict Resolution: 1.2.3
Draw.io: 2.2.0
Embedded Notes: 1.1.0
Extra Markdown editor settings: 1.10.1
Github Alerts: 1.0.5
Home Note: 2.1.1
Math Mode: 0.7.1
Note encryption: 1.1.1
Note list and sidebar toggle buttons: 1.0.3
Note overview: 1.7.1
Paginator: 3.0.2
Quick Links: 1.3.2
Remote-Note-Pull: 1.3.1
RevNav: 1.0.0
Rich Markdown: 0.16.0
Spoilers: 1.0.6
Table Formatter Plugin: 1.2.1
Templates: 2.4.0
Typograms: 1.0.3

Current behaviour

1. Sync with Joplin Server (no issues)
2. Add a larger file (seems to happen even with files that are just 90MB)
3. Hit Sync
4. Within just a few seconds, the client will timeout with

[warn] FetchError: network timeout at: https://joplin.mydomain.com/api/items/root:/.resource/c1ee5adb2d37430bb165a3b1ea9e220b:/content?share_id=BYdfIrZJjkAQUMD9Pc7
FetchError: network timeout at: https://joplin.mydomain.com/api/items/root:/.resource/c1ee5adb2d37430bb165a3b1ea9e220b:/content?share_id=BYdfIrZJjkAQUMD9Pc7
    at C:\Users\ldell\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\lib\node_modules\node-fetch\lib\index.js:1484:13

Expected behaviour

I expect it to keep on syncing until the file is uploaded (or the server-side times out), or, at least for this timeout value to be configurable in the client.

#10740 appears to confirm that this is a client-side issue. Additionally, I set all timeouts on the reverse proxy to 1hr to see if that fixed it, but it did not (which I expected since I also use the same reverse proxy for my nas and used to for nextcloud, which would never time out).

This also means that on slow connections, syncing just randomly fails on files since it's timing out. This timeout feature should be relative to the size of the file, and should be configurable by the user in the client settings.

Logs

No response