Thanks a lot for your answer. Since this is a browser-based application I don't think FTP or rsync/SSH are practicable alternatives, aren't they? Regards, Patrick Jonathan Zuckerman wrote: Probably not the answer you're looking for but I don't think that HTTP is the best protocol for what you're trying to do.. with files of that size, why not consider FTP or rsync/SSH? On Tue, Jun 16, 2009 at 8:56 AM, Patrick Herber<patrick.herber@xxxxxxxxxx> wrote:Hello! Thanks a lot for your answer! Unfortunately it seems that I'm really running against a timeout problem: Indeed with a slow connection I have this problem already with around 100MB, in my office (a good ADSL connection) I reach 250MB and directly in the same LAN of the Server I can upload 300MB in 10 minutes without errors... Thanks again and regards, Patrick André Warnier wrote:Patrick Herber wrote: ... Not really sure about this, so don't take it as gospel, but I believe that there may be some "maximum POST size" parameter built-in into Apache and/or Tomcat (as a protection against denial-of-service attacks). Maybe that is what you are running against, not a timeout.--------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx--------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx |