Well it’s a CDN, while you’re accessing the same url, you’re probably pulling it from a different server anyway. If only there was a service that would have rights management across widely distributed storage. One can only dream right? 
4 Likes
Yup. I see the 403 that @BrightSilence got from the NL CDN. The same URL is resolving
I guess I’ll open a ticket with the CND.
Thanks!
1 Like
It could even be called something like a “DDN”, perhaps? 
3 Likes
You should totally trademark this abbreviation
1 Like
@BrightSilence Already mentioned it in the topic “Initial Feedback” and @john already liked it 
1 Like
I know, hence my wink 
2 Likes
OK, we purged the image URL from the CDN cache, so it should be resolved for everyone now.
Please let me know if the problem persists.
1 Like
It showed on normal page load. But after CTRL + F5 it has vanished again.
Thanks so much, @jammerdan! It appears that the image had been removed from the original bucket, which explains why it was in some CDN caches and not others. I just uploaded the image again to the bucket and a test that I did with curl showed that the image URL failed before I re-uploaded the image and then worked afterward. I think this time I’ve fixed it.
Can you try it one more time?
I really appreciate your help and patience.
1 Like
I just tried again and it loaded normally and survived CTRL + F5 this time.
So it looks good now.
4 Likes
Great! Thanks again for your time and the report.
2 Likes