File names in frontend

Hi all,

First of all, hope this topic doesn't exist yet and it's not duplicate!

Going to the point, I just realised that any files/images that are uploaded to Media and then listed in the frontend, come with this "weird" prefix on their names:

https://{name_of_the_website}.cdn.prismic.io/{name_of_the_website}/64f54bc5-b232-44fa-85a6-adedabdabe6f_{file-name}.pdf

So the uploaded file name is {file-name}.pdf however when calling it in the frontend to be downloaded, the file name is 64f54bc5-b232-44fa-85a6-adedabdabe6f_{file-name}.pdf

I'm just trying to understand what this is and if there's something I can do to avoid this, as I have a download sort of system on my website and it's a bit "bad" to have this prefix on the file name (mainly for the end user who will download the files) =/

Thanks in advance!

Hi Pedro,

Thanks for reaching out.

I've checked the URL generated by Prismic for Images, for example, and here is how it looks like for me:

https://images.prismic.io/fdr-prismic-playground/e5953128-6fb9-41d0-8e14-2e5b0ffe50a9_test.jpg

Where the difference from what you have described is that the {name_of_the_website} is not repeated twice.

If I understand, correctly your question is that looking to have the file name separated from the auto-generated Image prefix such as 64f54bc5-b232-44fa-85a6-adedabdabe6f

Ok, for that, I will reach out to our production team to see what is the reason behind this choice.

Best,
Fares

I've gathered some information, and Prismic is used as a CDN for assets by many services. Then, the image URL should be unique, so we prefix assets with "64f54bc5-b232-44fa-85a6-adedabdabe6f" to avoid conflicts.

Hi Fares,

Yeah, I thought that could be the case and that probably nothing could be done to avoid or remove that. But it makes total sense!

Thanks!

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.