Hi! Not sure this is actually an issue with Prodigy – it looks like you might have No-Sniff Headers enabled in Cloudflare that prevents the browser from guessing the MIME type. Disabling that should solve the issue:
It's possible that there are places where Prodigy could set more explicity MIME types – however, you might still run into the same problems for your own custom content in HTML templates etc. if you're setting the no-sniff header.
We'll also include this by default in the next release.
Just note that there are potential open issues with this feature that may have an impact on the content – see this thread. There's also no reason you'd need to disallow MIME-type sniffing for Prodigy, since you're not hosting anything you don't control (e.g. user uploads).