Currently, if a RUFH PATCH requests gets interrupted, the error is swallowed by the bodyReader. This is not a problem for tus uploads, but leads to issues with RUFH uploads because a successful RUFH PATCH request with Upload-Complete: ?1 will set the upload length. If an interrupted PATCH is thus interpreted as successful, it will cause the upload length to be set to the offset at which the upload was interrupted and thus preventing the upload from being resumed.
This PR fixes this problem by not swallowing the error, making the handler aware of the interruption.
Currently, if a RUFH PATCH requests gets interrupted, the error is swallowed by the bodyReader. This is not a problem for tus uploads, but leads to issues with RUFH uploads because a successful RUFH PATCH request with Upload-Complete: ?1 will set the upload length. If an interrupted PATCH is thus interpreted as successful, it will cause the upload length to be set to the offset at which the upload was interrupted and thus preventing the upload from being resumed.
This PR fixes this problem by not swallowing the error, making the handler aware of the interruption.