The CORS headers seem fine, though I'm a little surprised about the content-type: $ curl -I https://bafykbzacedvzdo4hru3wul5excjthwjuz5ggd6jcs4wg77tg7bkn3c7h

The CORS headers seem fine, though I'm a little surprised about the content-type: $ curl -I https://bafykbzacedvzdo4hru3wul5excjthwjuz5ggd6jcs4wg77tg7bkn3c7hlvohq.ipfs.dweb.link/ HTTP/2 200 date: Thu, 28 Nov 2024 16:34:03 GMT content-type: application/x-rar-compressed content-length: 192215114 access-control-allow-headers: Content-Type access-control-allow-headers: Range access-control-allow-headers: User-Agent access-control-allow-headers: X-Requested-With access-control-allow-methods: GET access-control-allow-methods: HEAD access-control-allow-methods: OPTIONS access-control-allow-origin: * Can you try with another file? I do think that once I implement Helia's verified-fetch, issues like this should be less common.