From nobody@hyperreal.com Tue Mar 25 07:36:28 1997 Received: by taz.hyperreal.com (8.8.4/V2.0) id HAA03725; Tue, 25 Mar 1997 07:36:28 -0800 (PST) Message-Id: <199703251536.HAA03725@taz.hyperreal.com> Date: Tue, 25 Mar 1997 07:36:28 -0800 (PST) From: Tim Stives Reply-To: stives@netsos.com To: apbugs@hyperreal.com Subject: Problems viewing images with proxied service providers. X-Send-Pr-Version: 3.2 >Number: 255 >Category: os-linux >Synopsis: Problems viewing images with proxied service providers. >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue Mar 25 07:40:00 1997 >Last-Modified: Tue Mar 25 17:49:53 PST 1997 >Originator: stives@netsos.com >Organization: >Release: 1.2b7 >Environment: I am running Linux 1.3.81 and the apache 1.2b7. >Description: Several of my clients are having trouble viewing our pages from a variety of sources including buffnet.com and AOL. The text will load but the images will not. We were having the same problem before, so we upgraded to 1.2b7. This did not fix the problem. >How-To-Repeat: www.curtisscrew.com www.netsos.com >Fix: >Audit-Trail: From: Marc Slemko To: Tim Stives Subject: Re: os-linux/255: Problems viewing images with proxied service providers. Date: Tue, 25 Mar 1997 18:35:16 -0700 (MST) > Several of my clients are having trouble viewing our pages from a variety > of sources including buffnet.com and AOL. The text will load but the > images will not. We were having the same problem before, so we upgraded > to 1.2b7. This did not fix the problem. This is not a problem with Apache, but rather one with either your kernel or a router upstream of you. Any host sending a packet larger than a certain size can have this problem; it appears like either your kernel is broken or a router near you is eating large packets without sending back the appropriate ICMP message. Many old systems are limited to MTUs (the maximum packet length that can be sent to a remote system) of 256 or 512 for historical reasons. More modern systems have higher MTUs and try to automatically discover the proper one on the fly. Try an older and newer version of your Linux kernel and see if any of them fix the problem. If not, it is likely one of the routers upstream of you that is causing the problem; since you get your connection through uunet, they may be able to help if you can find the right person. As I said this is not an Apache problem, so we can't really help much more. State-Changed-From-To: open-closed State-Changed-By: marc State-Changed-When: Tue Mar 25 17:49:52 PST 1997 State-Changed-Why: Looks to be a kernel or router problem. >Unformatted: