Removing the WEBP cache vary

please explain a bit how does your avif work ?

I got a feeling you may not even need this

I’m using the imagify plugin which has converted all our images to .avif

I know , I mean how does it replace exiting image to avif ?

As far as i understand there are two options to choose from.

The first one is via rewrite rules.
The second one is via replacing the <img> tag with the <picture> tag which is the option I’m using right now.

I think on both method you don’t need webp vary

you can disable it in Image Optm -> setting -> webp replacement , set it to OFF

All settings in the image optimization tab are already set to OFF but the webp vary is still present in my htaccess file.

I even deleted and installed the litespeed plugin again, I tried to remove it manually but it still reapears each time in the htaccess file when i save any settings.

• This reply was modified 37 minutes ago by David.
• This reply was modified 36 minutes ago by David.

oh , did you enable guest mode/optimization ? that will forcefully add it

yes , that block will auto-recreate upon saving action

Yes guest mode/optimization is enabled.

It seems the only way right now is to change the permission of my htaccess file to 444 to prevent the vary from bering created again

• This reply was modified 35 minutes ago by David.
• This reply was modified 34 minutes ago by David.

well , actually you can just ignore it , since most of modern browser are webp supported , so it’s literally like every request is hitting webp vary

I didn’t know that. I thought the non-webp vary will be created alongside the webp vary too. So in this case you are right.

Thanks for your help

it kind of does that

if one browser has no webp access one page

and another browser with webp accessed same page, then there will be 2 caches for same page , this is called vary , in this case, webp vary

but it’s literally like 99% browser are webp support , so most of caches are fall to webp vary anyway