About an hour ago the frontend that one of my canisters is serving started serving the frontend as a file instead of a website. Did something change today in the way frontend is served?
Could you provide the canister ID?
If I call your canister directly with DFX, skipping the boundary node, the content-type response header is empty. Did you redeploy your canister today? Or this started happening without any changes to your canister?
Started happening without any changes to the canister or it’s frontend. Calling the canister with an agent works for me too.
https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.ic0.app/
Here is candid ui canister, its also getting served weirdly.
Thanks for sharing. It has the same underlying cause.
We’re investigating why this is happening now.
1 Like
Can you roll it back before investigating?
It’s uncertain what we should rollback until we find out what the cause is. If you want a fix as soon as possible, then the best thing to do would be to fix the missing content-type header that should be coming from the canister.
2 Likes
A fix for the boundary nodes is on the way. Additionally, a fix for the Candid UI canister is on the way. For any other canisters affected by this using an asset canister, I’d recommend making sure that your file extensions are correct, deploying to a local DFX instance and ensure that the content-type header is correct. If the file extension is correct but the content-type header is not, please let me know. Otherwise a fresh deployment with the correct file extension will fix the issue.
3 Likes
Putting a content-type header for the ‘/’ path file works and the website is now loading. Thanks for letting me know how to get it working asap.
3 Likes