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
In the recent amazon updates, there are a couple of changes in the AWS S3 API which is failing the S3 image upload in the editor.
When we upload an image it throws an error saying Parsing failed with status as CORS error.
As per the docs, the correct URL format is: https://<bucket-name>.s3.<region>.amazonaws.com
And the current URL formed is https://<region>.amazonaws.com/<bucket-name>
I had a look at the minified JS which computes this as: A.opts.imageUploadToS3 && (s = A.opts.imageUploadToS3.uploadURL ? A.opts.imageUploadToS3.uploadURL : "https://".concat(A.opts.imageUploadToS3.region, ".amazonaws.com/").concat(A.opts.imageUploadToS3.bucket)),
I believe this is a simple change and should be looked on a priority as things are breaking currently.
The text was updated successfully, but these errors were encountered:
# in your controller or helper
hash = FroalaEditorSDK::S3.data_hash(options)
hash[:uploadURL] = 'https://your-bucket.s3.your-region.amazonaws.com/'
return hash
But still doesn't work - still got 400 bad request.
I guess the lib and the docs are both very outdated? Please update these issues. Thank you.
In the recent amazon updates, there are a couple of changes in the AWS S3 API which is failing the S3 image upload in the editor.
When we upload an image it throws an error saying
Parsing failed
with status asCORS error.
As per the docs, the correct URL format is:
https://<bucket-name>.s3.<region>.amazonaws.com
And the current URL formed is
https://<region>.amazonaws.com/<bucket-name>
I had a look at the minified JS which computes this as:
A.opts.imageUploadToS3 && (s = A.opts.imageUploadToS3.uploadURL ? A.opts.imageUploadToS3.uploadURL : "https://".concat(A.opts.imageUploadToS3.region, ".amazonaws.com/").concat(A.opts.imageUploadToS3.bucket)),
I believe this is a simple change and should be looked on a priority as things are breaking currently.
The text was updated successfully, but these errors were encountered: