You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by lodewijkdans <lo...@dans.knaw.nl> on 2008/10/29 15:40:18 UTC
Upload exceeds maxsize error comes AFTER upload has finished
I am extending the upload component and have a problem with the maximum file
size detection. The mechanism seems to be working fine except for that it
has an user unfriendliness to it: An exception is thrown, an error message
is set and the onError event called, but the message only arrives AFTER the
upload has finished. Our maximum file size is 100 MB, so if I get a user
that is uploading a file of 200 MB he or she will have to wait until the
upload is finished before the maximum size exceeded error appears. This is
hardly user friendly and I cannot trust users reading and understanding the
disclaimer next to the upload button.
Does anyone already have a solution to this problem? How do I close the
input stream and output back the error? I can imagine that this would solve
the problem.
Another solution I can think of is trying to get the error back via Ajax,
but that is hardly an elegant solution. Then I could cancel the upload by
redirecting the uploading iframe.
Kind regards,
Lobo
PS I have tried this with the Jetty test server and have seen the problem on
virtually all browsers.
--
View this message in context: http://www.nabble.com/Upload-exceeds-maxsize-error-comes-AFTER-upload-has-finished-tp20228506p20228506.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Upload exceeds maxsize error comes AFTER upload has finished
Posted by lodewijkdans <lo...@dans.knaw.nl>.
Yes, I figured. That's why I implemented it this way:
* when the max size exception is thrown on the server the error is
registered
* that error is fetched by my custom progress requester
* when the error is detected the client side closes the iframe responsible
for the upload
this mechanism works perfectly.
thanks for your input though
Stefan Simik wrote:
>
> This is how things work in HTTP.
> One possible solution, that provides more control from client is flash
> upload - see http://swfupload.org/
>
--
View this message in context: http://www.nabble.com/Upload-exceeds-maxsize-error-comes-AFTER-upload-has-finished-tp20228506p20358820.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Upload exceeds maxsize error comes AFTER upload has finished
Posted by Stefan Simik <st...@gmail.com>.
This is how things work in HTTP.
One possible solution, that provides more control from client is flash
upload - see http://swfupload.org/
--
View this message in context: http://www.nabble.com/Upload-exceeds-maxsize-error-comes-AFTER-upload-has-finished-tp20228506p20347340.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Upload exceeds maxsize error comes AFTER upload has finished
Posted by Igor Vaynberg <ig...@gmail.com>.
this is how posts work. we do not get control until the browser has
processed the entire request. at least afaik.
if you want to fix it you will have to write a custom servlet that
processes uploads, and not use the standard POST mechanism.
-igor
On Wed, Oct 29, 2008 at 7:40 AM, lodewijkdans
<lo...@dans.knaw.nl> wrote:
>
> I am extending the upload component and have a problem with the maximum file
> size detection. The mechanism seems to be working fine except for that it
> has an user unfriendliness to it: An exception is thrown, an error message
> is set and the onError event called, but the message only arrives AFTER the
> upload has finished. Our maximum file size is 100 MB, so if I get a user
> that is uploading a file of 200 MB he or she will have to wait until the
> upload is finished before the maximum size exceeded error appears. This is
> hardly user friendly and I cannot trust users reading and understanding the
> disclaimer next to the upload button.
>
> Does anyone already have a solution to this problem? How do I close the
> input stream and output back the error? I can imagine that this would solve
> the problem.
> Another solution I can think of is trying to get the error back via Ajax,
> but that is hardly an elegant solution. Then I could cancel the upload by
> redirecting the uploading iframe.
>
> Kind regards,
>
> Lobo
>
> PS I have tried this with the Jetty test server and have seen the problem on
> virtually all browsers.
>
> --
> View this message in context: http://www.nabble.com/Upload-exceeds-maxsize-error-comes-AFTER-upload-has-finished-tp20228506p20228506.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org