A few weeks ago I added an image for the Digifile package type. It appeared to work when I did it, but now that image, and some others, appear to be broken. I don’t know if my edit broke something, or if it was already broken and I didn’t notice, but I thought I’d mention it, so someone can troubleshoot. Sorry, if it was me.
2 Likes
I don’t know what I am talking about… I just spot patterns. It may be a hint that the images that are failing have dashes in the file name, and the working images use underscores.
Doesn’t look like your fault. The server is doing something stupid. It redirects the HTTPS resources to HTTP which triggers the mixed content protection
2 Likes
2 Likes
Should be fixed now; in the redirect configuration that handles translations from a legacy path to the images, I forced the use of HTTPS in that redirect. Now, it appears nginx serves the image requests with a 200, and they display again 
3 Likes