Get net::ERR_CONTENT_DECODING_FAILED 200 (OK), start from yesterday our JS sometimes got this error

we put our JS on R2, and our domain using CF. Brotli already enabled. Can someone help me
2 Replies
Ivan Starkov
Ivan Starkov7mo ago
Same here. The error is random. From what I see this error is always for cached content. Cf-Cache-Status: HIT And Content-Encoding: gzip in response headers. And in our case it's also somehow related to r2 as original content is on r2 Reproduced even without cache: on r2 this image gives error https://pub-f0eceff175764d6daad6785b769f727b.r2.dev/stars_zoWSu63q603uN2jJgPjzJ.svg and this is not https://pub-f0eceff175764d6daad6785b769f727b.r2.dev/WS-logo-white_YEQ0Xbj7_5v5mHD2F_nt4.svg Also seems like all broken files has following metadata on r2
"Metadata": {
"atime": "2023-05-05T03:22:29.049615243+04:00",
"btime": "2023-03-25T03:30:05.129+04:00",
"filename": "blabla.svg",
"gid": "20",
"mode": "100644",
"mtime": "1679700605.129",
"uid": "501"
}
"Metadata": {
"atime": "2023-05-05T03:22:29.049615243+04:00",
"btime": "2023-03-25T03:30:05.129+04:00",
"filename": "blabla.svg",
"gid": "20",
"mode": "100644",
"mtime": "1679700605.129",
"uid": "501"
}
And all non broken has just Filename in the metadata The fix is to replace metadata
aws s3api copy-object \
--bucket assets-production \
--key check_DzyMpjZxBu1k6O8JoHeNK.svg \
--copy-source assets-production/check_DzyMpjZxBu1k6O8JoHeNK.svg \
--metadata-directive REPLACE \
--cache-control "public, max-age=31536004,immutable" \
--content-type "image/svg+xml" \
--metadata filename=check_DzyMpjZxBu1k6O8JoHeNK.svg
aws s3api copy-object \
--bucket assets-production \
--key check_DzyMpjZxBu1k6O8JoHeNK.svg \
--copy-source assets-production/check_DzyMpjZxBu1k6O8JoHeNK.svg \
--metadata-directive REPLACE \
--cache-control "public, max-age=31536004,immutable" \
--content-type "image/svg+xml" \
--metadata filename=check_DzyMpjZxBu1k6O8JoHeNK.svg
But we have sooo many files that I'm not sure we can do that
Kiki Y
Kiki Y7mo ago
Hi there, this is Kiki from Cloudflare. Sorry for this issue. We have a status page up now: https://www.cloudflarestatus.com/incidents/nzvw74126fp8 please follow up in status page for further updates.
Want results from more Discord servers?
Add your server