UploadAlreadyLockedException Encountered When Upload Resumes After Network Interruption #69
Description
Expected Behaviour
When a HEAD request is issued to resume an upload following a network disruption, a response with tus headers should be received.
Actual Behaviour
A UploadAlreadyLockedException is thrown and the upload is unable to proceed.
Steps to reproduce
In my case, I encounter this behavior due to the use of a VPN. In order to reproduce:
- select a relatively large file to upload
- connect to the VPN
- initiate the upload
- Disconnect from the VPN while upload is in progress (causing a network disruption)
- Subsequent HEAD requests are sent in an attempt to resume the upload, but tus response headers are missing due to
UploadAlreadyLockedExceptionobserved on the server.
The situation appears to be that described here. It would be great if this scenario could be handled seamlessly. Any thoughts on if this could be incorporated into the server?