Change Details

Apparently if a warning occurs on the first chunk that chunk isn't actually stashed and can't be continued (see T112405). Now as long as there aren't any security concerns is there a reason for this? Actually stashing the chunk could help cutting down the upload times as it doesn't has to upload the first chunk in case of a warning.

If warnings occur and aren't ignored during the upload of a chunk, the chunk is stashed as a separate "file" rather than being a part of a chunked upload session. It would be helpful if this separately-stashed chunk could be used as input to the chunked-uploading process so it wouldn't have to be re-uploaded if the warning is to be ignored.

Apparently if aIf warnings occurs on the first chunk that chunk isn't actually stashed and can't be continued (see T112405). and aren't ignored during the upload of a chunk, Now as long as there aren't any security concerns is there a reason for this? Actually stashing the chunk could help cutting down the upload times as it doesn't has to upload the first chunk in case of a warningthe chunk is stashed as a separate "file" rather than being a part of a chunked upload session. It would be helpful if this separately-stashed chunk could be used as input to the chunked-uploading process so it wouldn't have to be re-uploaded if the warning is to be ignored.