JFIF?

  • Resolved sous.studio

    (@sousstudio)


    2 years, 11 months ago

    Hey!

    My question is does EWWW-IO supports JFIF? And if so, shouldn’t we add jfif as file extension here (if NGINX is used)?

    location ~* ^.+\.(png|jpe?g)$ {
  add_header Vary Accept;
  expires 1y; log_not_found off; 
  add_header Cache-Control "public, must-revalidate, proxy-revalidate"; 
  add_header Access-Control-Allow-Origin *;     
  access_log off;
  try_files $uri$webp_suffix $uri =404;
}
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author nosilver4u

    (@nosilver4u)

    I’ve never tested using a JFIF file, but if they are indeed converted to WebP, then certainly change the first line to this:

    location ~* ^.+\.(png|jpe?g|jfif)$ {

    Thread Starter sous.studio

    (@sousstudio)

    I got it about the line. The question is – does it get converted with your plugin?

    Plugin Author nosilver4u

    (@nosilver4u)

    I did some more investigation on this and while I’m not 100% clear on the details, I found that most JPG images are in the JFIF format. That is to say, if you check most JPG images with a hex editor, they will have the JFIF signature in the file header because JFIF is the format used by most (if not all) modern JPG encoders.

    WordPress itself does not allow uploading files with a .jfif extension, and that isn’t the “normal” way JFIF is used. Rather, most JFIF files will use the more common .jpg or .jpeg extensions, and EWWW IO works perfectly well with these.

    However, if you DO have files on your WP site with .jfif extensions, and you find any functionality that doesn’t seem to be working, please file an issue at https://github.com/nosilver4u/ewww-image-optimizer/issues

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘JFIF?’ is closed to new replies.

Tags