This support forum is no longer in use. Please use the Cloudinary Community at to receive assistance from other members of the community and from Cloudinary's support team. For account-specific questions or if you believe that you've encountered a bug, please contact the Cloudinary team directly via the "submit a request" option on this support site.

Getting a 200 failed response due to CORS when renaming file



  • Avatar
    Stephen Doyle

    Hi Andrew,

    May I ask for some more information about what you're trying to do? It's not generally expected that our API methods will work from frontend code, with the obvious exception of the upload API method where there's a possible advantage to having the upload to Cloudinary come from the client's device directly

    For other methods, because the calls require an authentication signature to be created by your backend code, the call should also be made from the backend


    Comment actions Permalink
  • Avatar
    Andrew Randomsky

    Hello Stephen,

    Thanks for the response. I am using the rename functionality as a means of "deleting" files by moving them to a backup folder. I do have a signature that is created by our back-end (and appears to be generating correctly since I'm getting a 200 back), but you're right that this endpoint doesn't really have any advantage in calling it client-side vs back-end. I'll talk to my back-end folks about creating a new endpoint on our end to handle this.


    Comment actions Permalink

Post is closed for comments.