Don't send webp to CriOS when there is no accept:image/webp #1256
Comments
Note: a similar issue was found in #969 |
At this point maybe we should switch to a simple "send webp if and only if we get accept:webp"? |
I agree with that, but that's a larger change (assuming we still want to send webp to Android 4.0) and want to do that in a follow-up. |
Android browser supports WebP since 4.0 but doesn't have WebP header. It [1] On Thu, Jan 28, 2016 at 10:41 AM, Joshua Marantz notifications@github.com
|
It turns out we need to separately disable webp-lossless and webp-animated, so the full workaround is: SetEnvIf User-Agent CriOS mps_disable_webp |
More detailed workaround information for nginx and apache. None of this will be needed once we have 23947d0 in a release. Apache & mod_pagespeed 1.10: Nginx & ngx_pagespeed 1.10: 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: Nginx & ngx_pagespeed 1.9: |
accept:image/webp to send webp. Fixes #1256
accept:image/webp to send webp. Fixes #1256
The latest Chrome on iOS, based on WKWebView, cannot render webp images, but mod_pagespeed sends them.
See http://blog.chromium.org/2016/01/a-faster-more-stable-chrome-on-ios.html
I confirmed that this browser also does not send accept:image/webp. If, in the future, webp is re-enabled in CriOS, it will likely send accept:image/webp again.
This is a workaround:
SetEnvIf User-Agent CriOS mps_disable_webp
RequestHeader set ModPagespeedFilters -convert_jpeg_to_webp env=mps_disable_webp
The text was updated successfully, but these errors were encountered: