4 ms·
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
by dchest 5y ago
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
- mkl 5y agoMakes 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-respect-nosniff-for-page-loads/ 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.
- dchest 5y agoRight, nosniff doesn't apply to images.
- sandreas 5y agoShould be fixed, thank you!