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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
