That problem is causing us missing images in production. We are trying to understand why doesn’t this new url work on our website, but we also would benefit in knowing how to restore the old urls (except manually replace every image in the cms UI)
Is it possible that fetching the images from https://prismic-io.s3.amazonaws.com/... rather than fetching them from *.cdn.prismic.io results in worse performance? Where can we get info about the capabilities of Prismic's CDN?
My comment is deeply related to the original topic - I work in the same company as Alessandro
I'll recap the issue again.
When using Prismic's import feature, stored image URLs change from: https://<organization>.cdn.prismic.io/<image path>
to: https://prismic-io.s3.amazonaws.com/<image path>
I read cdn in the original image URL, which makes me think that you're using a Content Delivery Network (CDN) to serve the original image, whereas you're not using a CDN to serve the imported image. Is this correct?
To be clear, my question is not related to image transformation, it's related to how the image is served.
We removed SVGs from the imgix CDN due to security vulnerabilities, and they were moved to the amazon server and were treated as files, not images. They are the only image format served like this. Originally on the Amazon server, they weren't run through the CDN.
So there are some domains:
All images, except for SVG's , should be coming from images.prismic.io
SVG's should be coming from <repo-name>.cdn.prismic.io/<repo-name>
(if they are coming from prismic-io.s3.amazonaws.com/, then try to remove and re-add them to deliver them from<repo-name>.cdn.prismic.io/ and see if it works.)