Incorrect content-type
# r2
m
Yes… it’s one file… I created a cors rule and I’m accessing the file directly
s
Yeah can you send me that file if it isn’t sensitive? I’m not sure what’s so special about this. R2 will generally try to guess the content-type if you don’t supply one with your file. Can you also show me how you’re uploading these files? I’ll try doing the same thing then
Oh you just use Wrangler..
m
I discovered the issue
the issue is that the file was uploaded the first time without specifying the content-type
all the other times I've specified the content type but the cache didn't refresh
so it kept serving the first file (cached) instead of the version that It was visible in my R2 dashboard
s
Oh good! When you say “cached”, I’m assuming you mean you’re serving these assets from a public bucket via a zone with caching enabled? Because R2 is strongly consistent, and won’t cache things on its own
4 Views