Cancelling the Upload Leaves Partly-Uploaded File


I must admit that I'm using the APIs of the FileUpload directly and not the control but I'm guessing this behavior exists for both.
If I cancel a file upload part way through then I'm left with a half-baked file on the server. Is there a simple way to know that the connection was broken (on the server) so that the file can be deleted? I'm also not sure how resume works (maybe this is why files are left behind?).


Arkuzz wrote Jul 1, 2009 at 8:19 AM

I hope that remained file chunks means resuming enabled. If not, the component works bad. :(

ibrahimkurt wrote Jul 7, 2009 at 11:57 AM

hi Kevin, did you find any solution?

pcongdon wrote Aug 31, 2009 at 3:17 PM

In testing this solution, I selected a large file (about 2.5 G) for upload. I then cancelled the upload at about 380k. When I came back later and uploaded the same file I was prompted with "File Exists" message and allowed to continue the upload. However, what was uploaded to the web site was, in size, only about 1.4 G, not the complete file.

Then I removed the uploaded partial file and tried again with the same file and let it finish. This time it completed the upload and the file sizes matched.

Anyone else seen this behavior in testing the solution? I thought at first it only uploaded the size difference but the math doesn't work out ... :)

rodneypannell wrote Jul 12, 2010 at 12:32 PM

I could really use a cancelled event....that way if I want to just remove the file if the user canceled I can...or log a database event (something I need to do as well).

I think that would be a huge help.

wrote Jul 12, 2010 at 12:32 PM

wrote Feb 14, 2013 at 8:10 PM