I am seeing that aborted uploads (closing/refreshing the browser part-way through an upload) are automatically resumed even when s3FileCacheHoursAgo is not set. Is this expected functionality?
I thought if s3FileCacheHoursAgo is not set, the upload would start from the beginning instead of using the awsUploads localStorage cache?
I am seeing that aborted uploads (closing/refreshing the browser part-way through an upload) are automatically resumed even when s3FileCacheHoursAgo is not set. Is this expected functionality?
I thought if s3FileCacheHoursAgo is not set, the upload would start from the beginning instead of using the awsUploads localStorage cache?
Thanks