https://issues.apache.org/jira/browse/WICKET-3432
I provided a quickstart for this issue (uploading one or more large files
via Ajax) a while ago and Igor tested this with a file around ~700mb and
could not reproduce the issue. This issue persists for my team on multiple
OS flavors and across varying pieces of hardware (physical and virtual). The
workarounds we have applied have not completely resolved the issue.
I would like to request that this be re-opened or see if I can get some
folks (wicket users or the dev team) to try this quickstart in IE 8 (Windows
XP or Windows 7) with files up to 2G. For me, the issue occurs around the
~700MB mark. The symptom is that the file is uploaded to a temporary
directory, but the user is never directed to the response page. Firefox 3.6,
4 and Chrome work as expected.
Note that a non-ajax form submit for the offending file sizes works in IE as
expected, up to 2G.
If testing this item, I’d love ideas on what else could be contributing to
the problem, even if it possibly could be environmental. Although, we have
enough hardware diversity here to mitigate that possibility.
I’m even open to alternative upload strategies as a last resort, but I want
to avoid flash-based solutions and browser-specific solutions (if possible).
Regards,
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-3432-IE-Ajax-file-upload-tp3571293p3571293.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
