Re: New Chrome for iOS doesn't display webp anymore

145 views
Skip to first unread message

Joshua Marantz

unread,
Jan 28, 2016, 1:42:02 PM1/28/16
to mod-pagespeed-discuss, ngx-pagesp...@googlegroups.com
A fix is in trunk: https://github.com/pagespeed/mod_pagespeed/commit/23947d0006005c5e3aa7539d81b7819fdb454e4c

We are working on a release.

Also note that the previously stated workaround is insufficient: there are two more filters that need to be manually disabled in 1.10:

Apache & mod_pagespeed 1.10:
    # Temporary workaround for
    SetEnvIf User-Agent CriOS mps_disable_webp
    RequestHeader set ModPagespeedFilters -convert_jpeg_to_webp,-convert_to_webp_lossless,-convert_to_webp_animated env=mps_disable_webp

Nginx & ngx_pagespeed 1.10:
  http {
    pagespeed ProcessScriptVariables on;
    server {
      set $disable_filters "";
       if ($http_user_agent ~ CriOS) {
         set $disable_filters "convert_jpeg_to_webp,
convert_to_webp_lossless,convert_to_webp_animated";
       }
       pagespeed DisableFilters "$disable_filters";
    }
  }


In 1.9, there is no convert_to_webp_animated filter, and the nginx variable support is not present in PageSpeed so you have to completely disable webp until we get you a patch.

Apache & mod_pagespeed 1.9:
    # Temporary workaround for
    SetEnvIf User-Agent CriOS mps_disable_webp
    RequestHeader set ModPagespeedFilters -convert_jpeg_to_webp,-convert_to_webp_lossless env=mps_disable_webp

Nginx & ngx_pagespeed 1.9:
  http {
    pagespeed DisableFilters "convert_jpeg_to_webp,convert_to_webp_lossless";
  }


None of these workarounds will be needed if you rebuild from source and include the above patch.  We will update this thread when a release is ready.

On Thu, Jan 28, 2016 at 11:08 AM, Joshua Marantz <jmar...@google.com> wrote:
Note: Jeff informs me that in nginx we support a similarly surgical workaround in 1.10, but not 1.9.  

With ngx_pagespeed 1.10 (but not 1.9) it's possible to disable webp
just for chrome on ios:

  http {
    pagespeed ProcessScriptVariables on;
    server {
      set $disable_filters "";
       if ($http_user_agent ~ CriOS) {
         set $disable_filters "convert_jpeg_to_webp";
       }
       pagespeed DisableFilters "$disable_filters";
    }
  }

For ngx_pagespeed 1.9 you have to just disable convert_jpeg_to_webp until we send a patch (which is being tested now).


On Thu, Jan 28, 2016 at 7:55 AM, Joshua Marantz <jmar...@google.com> wrote:

On Thu, Jan 28, 2016 at 7:51 AM, Joshua Marantz <jmar...@google.com> wrote:
I have confirmed this workaround works in pagespeed.conf or .htaccess:

SetEnvIf User-Agent CriOS mps_disable_webp
RequestHeader set ModPagespeedFilters -convert_jpeg_to_webp env=mps_disable_webp
I reproduced the problem on an iPhone running the latest Chrome on iOS.  Then I put this workaround on modpagespeed.com and the problem is resolved.  I also confirmed we do still send webp to desktop Chrome.

I also confirmed that Chrome on iOS no longer sends Accept:image/webp, but evidently we are not looking for that when the user-agent contains CriOS, only when the user-agent contains Chrome.  We will work on a software patch as quickly as possible.

-Josh

On Thu, Jan 28, 2016 at 6:47 AM, Joshua Marantz <jmar...@google.com> wrote:

Thanks for trying this out.... I was concerned about this.  But I thought MPS would work correctly because we look for accept:image/webp.

We will send a conf file workaround today and also put out a patch soon after.

On Jan 28, 2016 5:58 AM, "Hans van Eijsden" <hans...@gmail.com> wrote:
See: https://productforums.google.com/forum/#!topic/chrome/NRZIV-ewuCU


Op donderdag 28 januari 2016 11:55:41 UTC+1 schreef Hans van Eijsden:
Yesterday, the new Chrome update for iOS was there, version 48.0.2564.87.
I don't like Chrome on iOS (Safari is faster), but I tried it and it doesn't display images on websites with ngx_pagespeed enabled anymore: webp.
The user agent string is this: "Mozilla/5.0 (iPhone; CPU iPhone OS 9_3 like Mac OS X) AppleWebKit/601.1 (KHTML, like Gecko) CriOS/48.0.2564.87 Mobile/13E5191d Safari/601.1.46"
Is it possible to blacklist it by myself? I don't want to disable webp for desktop Chrome users.
In the Chrome release notes I saw Chrome now using WKWebView, the newest Apple web rendering engine.

--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/28cc8a3d-0766-40c6-80f7-9a321ef8e77a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.




Reply all
Reply to author
Forward
0 new messages