So I am trying to deploy a zipped folder onto Amplify. The website in the zipped folder loads flawlessly on my computer. However, when deployed onto AWS Amplify, 3 images don't load. In developer tools in Chrome, I notice that those 3 images that didn't load get a 403 error. Every other image loads perfectly. Why would this happen?
#403 error for some images on only some images
static bronze
One thing I should mention is that all images, including the 3 images that won't load, are in the same directory.
Another interesting thing is that one thing I tried doing is to delete one of the images to see if I would get a 404 error when I deploy onto Amplify... but it still gives a 403 error for some reason.
static bronze
But replacing one of the broken images with a completely different broken image makes the image load properly on Amplify. Is possible that there's specific metadata in the image that Amplify just doesn't like?
Ok, so it seems that it is the case that Amplify doesn't like some metadata in some images... I fixed my issue by copy and pasting the images into a new Microsoft Paint image and then saving.
But why does Amplify not like metadata (in this case, photographer/camera metadata) in images? Why does metadata break images on websites deployed on Amplify?
halcyon dagger
@static bronze
static bronze
.webp? .png? .jpg?
It was .jpg