@uppy/aws-s3: Could not read the ETag header. This likely means CORS is not configured correctly on the S3 Bucket

[FlatMapIO]

Initial checklist

• I understand this is a bug report and questions should be posted in the Community Forum
• I searched issues and couldn’t find anything (or linked relevant results below)

Link to runnable example

Uppy React

Steps to reproduce

I searched the issue and found that this problem has been fixed several times.

However, I am still encountering the issue.

I used presign-url to upload files to R2 (S3 compatible), and I can see that the request returned the correct ETag in the Chrome network. However, when I debug the error point, I found that xhr.getAllResponseHeaders() did not retrieve the complete response header.

Deps:

"@uppy/aws-s3": "^4.1.3",
"@uppy/core": "^4.3.1",
"@uppy/dashboard": "^4.1.3",
"@uppy/drag-drop": "^4.0.5",
"@uppy/file-input": "^4.0.4",
"@uppy/progress-bar": "^4.1.0",
"@uppy/react": "^4.0.4",
"@uppy/xhr-upload": "^4.2.3",

Expected behavior

upload complete

Actual behavior

upload throws

[Murderlon]

Are you sure you have the correct bucket settings?

#5388 (comment)

[FlatMapIO]

Are you sure you have the correct bucket settings?

#5388 (comment)

For R2, it doesn't have these setting options. What I don't quite understand is that the information obtained from debug is inconsistent with the web response header. The Cloudflare R2 response already clearly includes these headers.