You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using OPTIONS, you can see that Cloudinary accepts Content-MD5 as a header when uploading a file. Currently, there is no way to add this or any other headers to a CLDUploadRequest. The Content-MD5 header seems like an important header to allow when uploading from iOS. The Cloudinary Rails/Active storage integration requires the MD5 be present, so this would bring the iOS client up to parity with the Ruby gem.
The text was updated successfully, but these errors were encountered:
Thanks for contacting us.
We have opened an internal task on our end, to add support for extra headers in the upload request.
Currently I don't have an ETA to provide, but I will update this thread with any new insights.
Thanks
Using OPTIONS, you can see that Cloudinary accepts
Content-MD5
as a header when uploading a file. Currently, there is no way to add this or any other headers to aCLDUploadRequest
. TheContent-MD5
header seems like an important header to allow when uploading from iOS. The Cloudinary Rails/Active storage integration requires the MD5 be present, so this would bring the iOS client up to parity with the Ruby gem.The text was updated successfully, but these errors were encountered: