I’ve been seeing this once in a while for a long time, but never got around to reporting it. It seems that some others have too - @mdridwan47 mentioned it in a comment that over 20 of us have liked now - I sure would like to see this get fixed:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Red X in place of user-posted images on article pages
- Thread starter CarlJ
- Start date
- Sort by reaction score
I too have noticed this issue for a long time, though haven't recently seen it pop up. For me, it happens when viewing the site on my Mac, as I rarely view it on an iOS/iPadOS device.
I wonder whether it might be a subtly corrupted file. Which browser are you using? The file displays correctly on my work PC (Edge on Windows 10). It's the Adium logo.
That image originates from another server, when the URL is provided (as part of the post), it's fetched to a content server, and loaded through a proxy service (perks: resolve non-SSL endpoints via SSL and provide tracking).
The entire URL is being passed in as a parameter, and it uses local caching to serve it up:
The original image file is sitting here (extracted from the image proxy param):
You can apparently toggle back to a direct image link (so it would use the above) vs. using the proxy and locally cached version (though losing the benefits I mentioned above).
Anyway, I've got just the image URL from here (i.e., proxy.php?<imageparams>) open in two different tabs, same browser, one is broken (aka, "red X"), the other is loading, I see that the headers are different. One is allowing a long duration to read the cached version, the other it first requiring a lookup to see if the original has been changed (that's via the cache-control and ETag headers). The tab that's "no-cache" is breaking, over and over, it's trying to resolve the resource and can't, while the other tab (and other browsers) are loading from the cache-server successfully.
Check into your cache control, expire time, anything about updates/patches to resolve caching/cache-control/header, etc., all the content/CDN stuff, assuming that's part of the hosting service and provided by Cloudflare.
The entire URL is being passed in as a parameter, and it uses local caching to serve it up:
Code:
https://forums.macrumors.com/proxy.php?image=https%3A%2F%2Fupload.wikimedia.org%2Fwikipedia%2Fcommons%2F9%2F91%2FAdium.png&hash=6b7d292a0413e216e1e64341bffda985The original image file is sitting here (extracted from the image proxy param):
Code:
https://upload.wikimedia.org/wikipedia/commons/9/91/Adium.pngYou can apparently toggle back to a direct image link (so it would use the above) vs. using the proxy and locally cached version (though losing the benefits I mentioned above).
Anyway, I've got just the image URL from here (i.e., proxy.php?<imageparams>) open in two different tabs, same browser, one is broken (aka, "red X"), the other is loading, I see that the headers are different. One is allowing a long duration to read the cached version, the other it first requiring a lookup to see if the original has been changed (that's via the cache-control and ETag headers). The tab that's "no-cache" is breaking, over and over, it's trying to resolve the resource and can't, while the other tab (and other browsers) are loading from the cache-server successfully.
Check into your cache control, expire time, anything about updates/patches to resolve caching/cache-control/header, etc., all the content/CDN stuff, assuming that's part of the hosting service and provided by Cloudflare.