Received: (from majordom@localhost) by hyperreal.com (8.8.4/8.8.4) id PAA26538; Mon, 7 Apr 1997 15:50:18 -0700 (PDT) Received: from valis.worldgate.com (marcs@valis.worldgate.com [198.161.84.2]) by hyperreal.com (8.8.4/8.8.4) with ESMTP id PAA26452 for ; Mon, 7 Apr 1997 15:50:07 -0700 (PDT) Received: from localhost (marcs@localhost) by valis.worldgate.com (8.8.5/8.8.5) with SMTP id QAA08766 for ; Mon, 7 Apr 1997 16:50:05 -0600 (MDT) Date: Mon, 7 Apr 1997 16:50:05 -0600 (MDT) From: Marc Slemko To: new-httpd@apache.org Subject: Re: general/232: Apache 1.2b7/b8-dev causes Netscape to display some jpeg's as broken images (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Mon, 7 Apr 1997, Rob Hartill wrote: > On Sun, 6 Apr 1997, Marc Slemko wrote: > > > Ok, so who wants to whine to Netscape this time about their lame browser? > > I suspect the bug is someplace else. > > My mod_perl header has never cause trouble with jpegs. I've been > using both for months. > > I cannot reproduce the problem and have no user bug reports. But do you have keepalives enabled? If I disable keepalives, the problem isn't there. Unless... perhaps there is an off-by-one error in either Netscape or Apache if the headers are of a certain length? The headers are right around 255 bytes long... hmm... Perhaps I will make a test server with nc that sends headers that long... aha. Ok, I have managed to reproduce it without Apache. Sending these headers: HTTP/1.1 200 OK Date: Mon, 07 Apr 1997 22:34:44 GMT Server: Apache/1.2b8-dev mod_perl/0.94xxxxxxxxx Last-Modified: Fri, 14 Mar 1997 22:18:18 GMT ETag: "1c27e-fe8-3329ceaa" Content-Length: 4072 Accept-Ranges: bytes Connection: close Content-Type: image/jpeg with the arthritis.jpg file (http://www.enews.com/graphics/covers/arthritis.jpg) appended after that, using a server of: cat file | nc -l -p 8080 where nc is Hobbit's netcat caused Communicator 4.0b3 to display the broken image icon. If I added one more character to the server name, it was still broken, but if I added another one to that it was ok. Further experimenting shows that it is when the headers reach 257 bytes that the problem pops up. My money is on a bug in Netscape's software.