Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 86568 invoked from network); 6 Apr 2002 13:05:05 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 6 Apr 2002 13:05:05 -0000 Received: (qmail 6416 invoked by uid 97); 6 Apr 2002 13:04:48 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 6396 invoked by uid 97); 6 Apr 2002 13:04:48 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 6385 invoked from network); 6 Apr 2002 13:04:47 -0000 Message-ID: <001701c1dd6b$98ede050$9d02020a@gregorym2k> From: "Matt Gregory" To: "Tomcat Users List" References: <000001c1dd59$91337120$3100a8c0@developers.local> Subject: Re: Tomcat corrupts file during download Date: Sat, 6 Apr 2002 08:04:33 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Are you downloading the file with a jsp page? It should be noted that if you write to the output stream of a jsp page: [HttpServletResponse/ServletResponse.getOutputStream()], then the output stream returned is a character output stream and will mangle binary files and not handle all output correctly. Just thought I would point that out since it gave me some serious headaches. ----- Original Message ----- From: "Dan Gabdullin" To: "'Tomcat Users List'" Sent: Saturday, April 06, 2002 5:55 AM Subject: RE: Tomcat corrupts file during download > Hello > > >If this problem indeed exists, then it is a JVM problem. Tomcat > obviously > >can't make a difference it is sending bytes on the LAN or on a WAN, and > >doesn't do anything unusal when it comes to bytes output. > >That being said, some people are actually using TC on the internet > without > >corruption or any problem, so I think even if you think it is not your > >fault, it is a configuration issue on your side. I'm regularly closing > bug > >4668 for that reason. > When I use Tomcat from the Internet I don't have the problem with > corruption either. The bug appears only when I connect from the LAN to > the server in the same network using Tomcat's WAN IP address. This is > not a common situation and it doesn't really spoil the work. I can > always connect using LAN server IP address. But the bug is in Tomcat for > sure. I used IIS and Apache and no problems appeared. I tried to use > Jetty, which is 100% pure Java HTTP server, and it didn't corrupt the > file either, so the problem is not in JVM. > I don't think that the problem lies in network configuration. In such a > case none of the above servers would have worked. > > Best regards, > Dan > > > -- > To unsubscribe: > For additional commands: > Troubles with the list: > > -- To unsubscribe: For additional commands: Troubles with the list: