As mentioned in the thread, only the client/user agent (browser) can abort the upload. I am using Ajax to monitor the upload and when I feel the upload is not going to be successful (my own criteria) I display a upload error message with a link to another page. Like so someurl Please abort upload so that the user can 'move' away from the upload. Not very elegant, but the only hack i could think of. HTH. Salman Khattak
david2 wrote: > > How does one go about "forcing" the connection closed from the Client > side? I am running into problems with connections not being close when > used by Axis, but can't find a way to trigger > HttpMethodBase.setConnectionCloseForced (a protected method) from being > sent. Any ideas? > > Thanks, > -David > >> The HTTP Protocol is the limiting factor here. Any request or response, >> once started, has to complete before either side can send anything else. >> The only way to stop it sooner is to force the connection closed, >> accomplishing a TCP level RESET, but you also lose the ability to send >> any >> response whatsoever to the request. > > -- View this message in context: http://www.nabble.com/-fileupload----aborting-file-upload-tf2640397.html#a10378254 Sent from the Commons - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
