Hacker News new | past | comments | ask | show | jobs | submit login

That's probably because OP's server doesn't serve a correct Content-Type header for AVIF and also disables content type sniffing.

Needs:

  AddType image/avif .avif



Makes sense for Chrome's behaviour, but that means Firefox is ignoring the "X-Content-Type-Options: nosniff" header, which it supposedly respects: https://blog.mozilla.org/security/2020/04/07/firefox-75-will...

Also, upon further investigation, I think both browsers are displaying the AVIF for me. It has quite a bit less detail than the JPEG, so it's identifiable.


Right, nosniff doesn't apply to images.


Should be fixed, thank you!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: