Getting a 200 failed response due to CORS when renaming file

Follow

Andrew Randomsky

• October 13, 2022 17:21

I'm running into an unusual issue with my rename request where it successfully renames the file, but I get 200 fail response back due to CORS. It appears that the Access-Control headers are missing from the rename endpoint. You can compare my response headers for a successful upload request (left) and my failed rename request (right) here: https://www.diffchecker.com/bgMAWg9R

Any insight into this would be greatly appreciated! Thank you!

0

• 

  Stephen Doyle

  • October 14, 2022 09:43

  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

  Regards,
  Stephen

  0

  Comment actions Permalink
• 

  Andrew Randomsky

  • October 14, 2022 14:49

  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.
  
  Thanks!

  0

  Comment actions Permalink

Post is closed for comments.