WEBP Safari

Hi,

the rule you posted is out-dated already

may I know what is your LSCWP version ?

please try disable webp and then re-enable it , it should give you the new rules and please try how it goes

### marker WEBP start ###
RewriteCond %{HTTP_ACCEPT} "image/webp" [or]
RewriteCond %{HTTP_USER_AGENT} "Page Speed"
RewriteRule .* - [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp]
RewriteCond %{HTTP_USER_AGENT} iPhone.*Version/(\d{2}).*Safari
RewriteCond %1 >13
RewriteRule .* - [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp]
### marker WEBP end ###

Best regards,

Hi,

Yes , iPhone/iPad users generally have very much percentage on up-to-date version

MacOS Big Sur is still on beta though

if you still got issue , could you please post the .htaccess rule between

### marker WEBP start ###

adn

### marker WEBP end ###

Best regards,

Hi,

1) why would you want to do this ?

if you want to disable webp , just disable the option in setting

2) do you use CDN ? if no CDN in use , I have a workaround for you

Best regards,

Hi,

Could you please tell me, how should be renamed my files
Options:
Original >> Result without webp (Safari)
1. filename.jpg.webp >> filename.jpg
2. filename.webp >> filename.jpg

this won’t work that way, if you re-name both webp and origin to same file name , then you are back to your origin issue and safari will get webp if you do this , or chrome won’t get webo anymore.

1) yes and no , that’s why I asked if you are using CDN

when you use CDN , CDN node will cache the jpg/webp file , so your rewrite rule won’t be even in use.

I understand your idea was like this :

Chrome -> access *.jpg -> redirect to *.jpg.webp

Safari -> access *.jpg -> keep it

Safari -> access .*.jpg.webp -> *.jpg

but , on second step , cloudflare will directly serve the file regardlessly it is webp or jpg , so the request doesn’t hit on your origin server for your rewrite rule to be used.

as matter of fact, I have made that rule already , but it just won’t work with cloudflare or other CDN , currently I only know BunnyCDN can vary content on accept header

2) it doesn’t rename anything , this is how LSCWP webp works

when you do image opt , it will generates file like this

image.bk.jpg -> this is backup file

image.jpg -> origin file with optimization

image.jpg.webp -> webp version

by design , when browser sends “accept: image/webp” header , then server sends webp files , if this header not present , then don’t send webp

3) not sure what is it ?

Best regards,

Hi,

1) yes , currently as for CDN, I only know BunnyCDN can vary it , or CloudFlare with enterprise plan , but you know the price for CF enterprise…

2) you don’t need to re-name it , LSCWP will search for .webp in that form

image.bk.jpg -> this is backup file

image.jpg -> origin file with optimization

image.jpg.webp -> webp version

3) it will end up SAME OUTCOME as I have mentioned about CDN service.

the file is cached already on CDN , so whatever rewrite rule you put in your origin , it just will not be used at all

4) picture tag , yes, it is the best solution , but unfortunately LSCWP doesn’t support that way as of now. 🙁

Best regards,

Hi,

1) currently no , but this is on the to-do list.

2) you do NOT need to 2.3 and 2.4 , if your webp is generated by LSCWP , LSCWP will keep

image.bk.jpg -> this is backup file

image.jpg -> origin file with optimization

image.jpg.webp -> webp version

this structure , webp will only be called by PHP when detects supported browser.

were your webps generated by LSCWP ? or by other plugins ?

do you see the files in structure as I mentioned ?

Best regards,

Hi,

if you want to use LSCWP webp replacement , you just need to put the file in that structure

Best regards,