Well, ordinarily you'd just refresh or shift refresh if that happened, but now there's a proxy that caches a broken copy of a photo with no way for the user to tell it to re-fetch. Have to wonder what exactly it is - maybe anti DDOS or something kicking in at their end if it gets a whole bunch of requests coming from some mysterious cloudflare thing? In any case it doesn't seem to be a failure on the upload/storage side at abload, all the 1024 thumbs still actually work at the link, it's just that in the event of a failure to download, that failure gets stored in the cache.

Thanks Amin for looking into the problem btw. I think it might just be a circumstance of the exact time of the post at the exact moment abload fails to send the whole picture - eg if it's just at that exact picosecond the proxy requests it that abload has a failure then it's stuck with it.

Thanks Amin for looking into the problem btw. I think it might just be a circumstance of the exact time of the post at the exact moment abload fails to send the whole picture - eg if it's just at that exact picosecond the proxy requests it that abload has a failure then it's stuck with it.

Click to expand...

I think you're probably right. Not sure what can be done about it. If we don't proxy the images, we can't be https without browser warnings and such.

I've been doing some more testing, and unfortunately abload.de is very hit and miss. A lot of times the images don't fully load, and like you said, the proxy preserves the failures.

Click to expand...

I paste the same set of links on multiple forums so I have examples where I can test 30 something images just by forcing refresh on one page and I've not been able to generate a failure pulling images straight from there at all so far (or even image threds like neogaf's PC highres screenshot thread where there'll be ~100 6mb+ pics per page and all of 'em load fine). I mean, I don't doubt that there's an issue you're seeing because the proxy copy is right there as proof, just, it's not something I've been able to replicate since seeing the first one stick in the cache the other day, and I've been trying

My setup is that I generally upload in chrome and browse in a locked down firefox (privacy badger/https everywhere/adblock/noscript) so I'm pretty much never seeing a cached copy of anything I've uploaded when I first browse an image thread - this stuff with the proxy is the only time I've seen it fail the whole time I've been using it for photo uploads and that's from pretty much since I started posting here. Hopefully it is a temporary glitch

Links in this page may be to our affiliates. Sales through affiliate links may benefit this site. We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.