RadUpload ProgressArea Bugs

[Kræn Munck]

First bug:
If your request exceeds maxRequestLength, RadProgressArea does not show up at all..

Making this example code useless:
http://www.telerik.com/help/aspnet-ajax/upload-how-to-client-file-size.html

And since all requests are completed either way i'm not inclined to increase my httpRuntime maxRequestLength any further.

And i'm not sure i would want to let users "cancel" their uploads when they are not really being cancelled, but lingering and consuming bandwidth.

Second bug:
If you should decide to display the cancel button, you'll notice that any subsequent attempt at uploading leaves the ProgressArea at a fixed position of where it was last cancelled.

[Dimitar Terziev]

Hello Kræn,

In general when the size of the uploaded file exceeds the maxRequestLength, an error occurs and it's expected that the RadProgressArea is not shown. This is the default behavior.

You have stated that all of your requests are completed. Could you elaborate a bit more on this statement. Do you mean that files with size bigger that the allowed one are being uploaded successfully. As I have mentioned above, if a file execeeds the maxRequestLength you should get the "Page not found" error. This is why the maxRequestLength property is being used.

As for your second problem, I've managed to reproduce it and we shall investigate it further. It seems that when the upload is canceled trough the progress area the page is left in some intermediate state. This is why it's appropriate to refresh it before you start another upload.

If you want to be able to cancel the uploading process it's more convenient to use the RadAsyncUpload contro rather than the RadUpload.

Regards,
Dimitar Terziev
the Telerik team

[Kræn Munck]

I guess i mean, it succesfully transmits data until it hits the limit :)

We turned on the progress area because our limit of 10 MiB is quite high, and upload bandwidth for users is always alot smaller than download bandwidth. So to avoid users frantically clicking the submit button expecting their (job applications in this case) to instant upload, we'd like to keep them in the loop..  even if it will fail when hitting 10 MiB .. it's better than keeping them in the dark..

We have measures in place to display a nice error message that they picked files that were too large.

Will the RadAsyncUpload Control solve any of these issues?

Won't the post's run till the limit anyways? or can you terminate the posts clientside when it's an ajax post?

[Peter Filipov]

Hi Kræn,

In your case you could use the RadAsyncUpload, because the control can validate the file size on the client side. Please review the following demo.

Regards,
Peter Filipov
the Telerik team