This bug appears to affect Safari 7.xx and does not affect Safari 6.xx. If you go to the URL above on Modular Fords website, the pictures in the thread will be briefly visible as you open the thread and then they disappear leaving only the little blue boxes with ? inside. I created the thread at the URL with Safari 6.xx. When I view it with Safari 7.xx it fails to image the pictures on that thread and many other threads on the same and other websites. The pictures are visible with FireFox and IE but not Safari, Chrome or Opera. The website uses VBulletin as their engine which is a very popular website hosting engine. You should be able to reproduce the error easily by just opening the url.
I can verify that the behavior described in this ticket is still present in r186279 (and also Chrome 43.0.2357.134). This problem is occurring because the server is setting the Content-Length header for the images larger than they are supposed to be which then causes a load error after the transfer times out after several seconds. As an example, the first broken image from the thread http://www.modularfords.com/attachment.php?attachmentid=84722&d=1324949965 has a Content-Length value of 97010 but it looks like it really should be 56250. The incorrect Content-Length also causes problems when trying to download the image using curl by running "curl http://www.modularfords.com/attachment.php?attachmentid=84722\&d=1324949965 > /dev/null" which then generates the following output: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 57 97010 57 56250 0 0 179k 0 --:--:-- --:--:-- --:--:-- 180k curl: (18) transfer closed with 40760 bytes remaining to read Perhaps for incomplete image transfers WebKit should be altered to try displaying the images using whatever data it was able to retrieve? That seems to be what Firefox does. If that sounds reasonable, I think I could make a patch to do that.
I am unable to reproduce this in Safari 15.5 on macOS 12.4 and URL load picture completely fine and it remains visible and does not show any "blue box with ?" as mentioned within Comment 01. I think it is something which got fixed along the line. Can we mark this bug as "RESOLVED CONFIGURATION CHANGED". Thanks!
Thank you for checking!
While I appreciate your follow-up, the original bug was reported seven years ago! I think the problem has been long since resolved.