Users have complained a few times about seeing a bizarre set of pink or green stripes on our webpage. At first I thought there were a rash of video card outages, but then someone sent me a screenshot from their browser (IE8). I later saw the same thing, but with slightly different colors on Chrome. Users have experienced this on their iPads and iPhones (iOS Safari). Because I've optimized the site to cache images, the bad image stays around until you clear your cache, so once you do, it resolves itself. My assumption is that the transmission of the image is being cut off mid-stream and then staying that way, but I can't for the life of me figure out why. Here's what I've checked:Header length is being sent, and transmission looks okay (wget sample below): wget http://www.superiorlivestock.com/templates/sla2/images/wallbg2.jpg--2012-04-05 08:46:00--  http://www.superiorlivestock.com/templates/sla2/images/wallbg2.jpgResolving www.superiorlivestock.com (www.superiorlivestock.com)... [ip redacted]Connecting to www.superiorlivestock.com (www.superiorlivestock.com)|[ip redacted]|:80... connected.HTTP request sent, awaiting response... 200 OKLength: 45926 (45K) [image/jpeg]Saving to: `wallbg2.jpg'Images are not being served gzipped (apache conf below):SetOutputFilter DEFLATESetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip dont-varyThe site is www.superiorlivestock.com, and here's a sample of the bad page load:Is there something obvious I'm missing? Am I saving my images in the wrong format somehow?
Bizarre image loading problem from apache2
images;apache2;gzip
The first thing I noticed when I looked at your page in Firebug is that some of your images (specifically this one, which toomanyairmiles already posted a screenshot of, and this other one) are simply huge — the first one is 4.2 megabytes!When I first loaded the page, the huge image was corrupted, more or less like in toomanyairmiles's screenshot.  When I reloaded the image, it downloaded correctly.  However, curiously, in both cases the image file I got was 4,362,346 bytes long; it's just that, in the broken version, after 3,903,489 bytes the correct image data stopped and was replaced by something else (which, alas, looked just like random bytes — or compressed JPEG image data — in a hex editor).Anyway, I suspect that resaving those few huge images at a more reasonable size should at least make the problem occur much less frequently, even if it won't actually fix the underlying cause of the data corruption.  As a bonus, your website will also load faster.