R2 error "net::ERR_CONTENT_DECODING_FAILED 200 (OK...
# r2s
Sid | R2
05/25/2023, 4:01 PMHave you created a ticket already? If not, can you do so so it can be escalated? That broken file might be of help too!
k
kev-ac
05/26/2023, 8:35 AM@User No, I haven't, but I also can't on the free plan for R2 related issues.
The file itself doesnt seem to be broken, so attachment it to a ticket would not be of a great help, I think. The problem lays in the stored version of it in R2.
s
Sid | R2
05/26/2023, 10:37 AMOkay let me see if I can get one made for you. Can you describe the problem here just so it is in one place?
k
kev-ac
05/26/2023, 12:36 PMSure. The problem is that certain files in a bucket can no longer be accessed because of a "net::ERR_CONTENT_DECODING_FAILED 200 (OK)" error in Chrome (other browsers throw a similar error as well). The files were all uploaded in January 2023 and worked fine for some time. If I download said files from the Cloudflare dashboard and reupload them as it is they also work fine. So something must have happened to these files in the meantime which made them unaccessible on the public URLs.
kev-ac
05/26/2023, 12:37 PMBroken file: https://pub-7e722c392cb24f389b2941db8812a3f0.r2.dev/test-files/file_4m.txt
Same file but reuploaded: https://pub-7e722c392cb24f389b2941db8812a3f0.r2.dev/test-files/test-files_file_4m.txt
kev-ac
05/26/2023, 12:37 PMBoth uploads (broken and new) were made through the Dashboard.
kev-ac
05/26/2023, 12:38 PMThe file contents are not important for this issue, because the use case for us here is just its defined size to measure user network speed.
The contents were generated by something like /dev/urandom, so look garbled on purpose.
2 Views