Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.mixmin.net!hq-usenetpeers.eweka.nl!81.171.88.15.MISMATCH!eweka.nl!lightspeed.eweka.nl!193.141.40.65.MISMATCH!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <2918885.X1uCrcLdkc@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Wed, 03 Oct 2012 20:20:53 +0200 User-Agent: KNode/4.4.11 Content-Transfer-Encoding: 8Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. <2953112.VveF1GjdCU@PointedEars.de> <5065817e$0$6883$e4fe514c@news2.news.xs4all.nl> <6300879.mfXoyHR8pD@PointedEars.de> <506a0d4c$0$6932$e4fe514c@news2.news.xs4all.nl> <1504793.Zb9mryafdB@PointedEars.de> <506c70ad$0$6930$e4fe514c@news2.news.xs4all.nl> Followup-To: comp.lang.javascript MIME-Version: 1.0 Lines: 68 NNTP-Posting-Date: 03 Oct 2012 20:20:54 CEST NNTP-Posting-Host: b1f40628.newsspool3.arcor-online.net X-Trace: DXC=TI@j=@gQ\DTcHPTNZh_e7QMcF=Q^Z^V3X4Fo<]lROoRQ8kF?b02nZSMIK`IcM37_Y X-Complaints-To: usenet-abuse@arcor.de Xref: csiph.com comp.lang.javascript:16351 Tom de Neef wrote: > "Thomas 'PointedEars' Lahn" wrote: > […] I need to get the html
submit alternative working because that > _is_ the fall-back. And I could not get it to work. Then you are doing something wrong server-side, or have not explained your goal in enough detail. >>> So I played around with >>> >> enctype="multipart/form-data"> >>> >>> >>>
>>> >>> And it works: a true copy of the selected file ends up on the >>> server. Ain't that marvellous! >> >> Of course. That has worked at least since HTML 4.01 became a W3C >> Recommendation (1999). > > Still: marvellous ! :) > The key problem: >>> using the form submit, the connection will be terminated (gracefully) >>> after the upload. > > As you have responded: it should not ! Evidentially it *will not*. Not with a HTTP/1.1 client. > And I have failed to find the cause. I wonder how you get the idea that the connection would be terminated in the first place. ISTM you are confusing HTTP with TCP. HTTP is stateless; TCP is not. > But I have found a workaround: in the
element I now specify a > hidden