I don't even know where to begin for this rather unusual bug that I've come across. I use an image host where I can hotlink directly to the images I want to use, and it's got this weird and unusual behavior when it fetches images that I've embedded into my articles, the link errors to a 403 Forbidden when loading the image from the link I've given it, but links are public facing and accessible to anyone if they know the URL, so hot linking an image embed should just work right? ...Well that doesn't appear to be the case here, it shouldn't be erroring with 403 Forbidden, however if I visit the URL of the hot linked image I've embedded, only then does it somehow show the image on the article properly and not error on 403 Forbidden. I did multiple testings and the results appear to be the same every time, and this is definitely a World Anvil bug when fetching resources from URLs when they're known to work and is publicly accessible. Tested this in a clean browser state, one that hasn't ever visited World Anvil or an article on World Anvil at all, no cached images or history and try visiting the page that it has the hot linked image source from that image will fail to load because it's erroring on 403 Forbidden and this is apparent when looking at the Console Log, I have found it to also be somewhat inconsistent at times too in other browsers, I mainly and primarily use Firefox, and have tried with "Other" Chromium based browsers, even if you didn't visit the URL source it didn't error on, it may sometimes load without erroring on 403 Forbidden, and from what I can see it doesn't seem to be an issue of the image host either as the links always appear to be working with little to no downtime.
1. Clean state browser of your choice. 2. Visit an article with public facing URL hot linked embedded images. 3. View your Browser Console where the images fail to load. 4. Visit the source of that image and then refresh on the article page to see it show up after.
Can you please give us an example so we can investigate - there is nothing for us to action on above report. The only thing I can say is that we cannot be responsible for outside sources but that would be useless and I do not want to do that In order for us to test we'd need to have something to go on with.
Closed due to no response for over 30 days. Please feel free to reply here so we can investigate