Optionality fof the asset version in the URL string

Comments

1 comment

  • Avatar
    Raz Ziv

    Hey Alexey,

    If you are getting an error when trying to access the URL without the version component, it means that this URL was error cached prior to your request. It can happen when you try to access the URL before the asset has finished uploading to your account or if it was deleted yet you haven't yet uploaded a new asset using the same public_id.
    If you would like to read more about Cloudinary's 4xx error caching mechanism, you can refer to the following article.

    With that being said, I've just accessed both URLs from my machine and was able to get the image returned in both cases, so it is most likely that the error caching has now expired. Please check again to see if you are now also able to access the URL without the version component. In case that you still get the error, please try and clear your local browser's cache or try accessing from a different browser.

    Generally speaking, if you prefer delivering your assets with non-versioned URLs, it is best to store the `public_id`, `resource_type`, and `type` attributes as returned in the upload requests' responses and then generate the URLs using our designated methods provided in each of our SDK libraries.
    Please note that by default, our SDK libraries do not add a version to the generated URLs, unless the asset is stored within a folder hierarchy, then a `v1` version is added. You can also disable this functionality by adding the following parameter to your request `force_version: false` (syntax differs depending on which SDK you use).

    If you need further assistance with setting this up, feel free to let me know. You can also open a direct support ticket at https://support.cloudinary.com/hc/en-us/requests/new in case you would like to share additional information over a private channel.

    0
    Comment actions Permalink

Please sign in to leave a comment.