Announcing ngx_pagespeed beta release 1.11.33.0

[Jeff Kaufman]

The first beta release of ngx_pagespeed 1.11 is now available. This
release targets users on mobile devices and low-bandwidth networks by
adding Save-Data support. Save-Data is a new Client Hint that allows
site visitors to indicate that they would prefer lower-quality
resources in order to save data. [1] Sites are most likely to see
requests to save data today from visitors who have turned on Data
Saver mode in Chrome [2] or the equivalents in Opera and Yandex
Browser, often because they're on slow or expensive connections. Now,
with 1.11, when such a user comes to your site asking it to save data,
ngx_pagespeed will compress images to a lower quality level [3] than
it would typically, decreasing their size further at the cost of
slightly more image distortion.

[1] https://developers.google.com/web/updates/2016/02/save-data
[2] https://developer.chrome.com/multidevice/data-compression
[3] https://developers.google.com/speed/pagespeed/module/filter-image-optimize#image-quality

Installation Instructions

See https://developers.google.com/speed/pagespeed/module/build_ngx_pagespeed_from_source

The installation process is the same even if you've already installed
a previous version.


This release also resolves several issues:

Issue 973: Strip subresource hints
https://github.com/pagespeed/mod_pagespeed/issues/973
https://github.com/pagespeed/mod_pagespeed/commit/d0bae68
https://github.com/pagespeed/ngx_pagespeed/commit/08e284f

Issue 1214: PageSpeed console blank
https://github.com/pagespeed/mod_pagespeed/issues/1214
https://github.com/pagespeed/mod_pagespeed/commit/2bd239d

Issue 1276: CSS Parser has off-by-one heap read
https://github.com/pagespeed/mod_pagespeed/issues/1276
https://github.com/pagespeed/mod_pagespeed/commit/0bc4ce7

Issue 1277: Google Fonts CSS inlining broken
https://github.com/pagespeed/mod_pagespeed/issues/1277
https://github.com/pagespeed/mod_pagespeed/commit/e3aa7b7

Nginx Issue 1064: Multiple Vary headers emitted
https://github.com/pagespeed/ngx_pagespeed/issues/1064
https://github.com/pagespeed/ngx_pagespeed/commit/b081bb7

Nginx Issue 1151: Unclear message on ParseUrl failure
https://github.com/pagespeed/ngx_pagespeed/issues/1151
https://github.com/pagespeed/ngx_pagespeed/commit/6634754

Jeff Kaufman
PageSpeed Team, Google

[Centmin Mod George]

Jeff could you clarify for https://developers.google.com/speed/pagespeed/module/filter-image-optimize#image-quality

that whether JpegQualityForSaveData and WebpQualityForSaveData are enabled by default if not specifically set to enabled ? or does one require to specifically enable these options for them to take affect ?

thanks

George

[Jeff Kaufman]

They're enabled by default. If a visitor sends the "SaveData" client
hint we'll use quality 50, while otherwise we'll use quality 85 (80
for webp) for desktop and 70 for mobile.

If you want to disable this feature, you can set
JpegQualityForSaveData and WebpQualityForSaveData to -1.

> --
> You received this message because you are subscribed to the Google Groups
> "ngx-pagespeed-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ngx-pagespeed-di...@googlegroups.com.
> Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
> For more options, visit https://groups.google.com/d/optout.

[Hans van Eijsden]

Thanks for the update!

Are you sure to have issue 1064 solved? I still see this:

$ curl -I https://www.weblogzwolle.nl/A.components,,_com_jomcomment,,_templates,,_boxy,,_comment_style.css+templates,,_weblogzwolle,,_css,,_template_css.css,Mcc.IAezBGjcN3.css.pagespeed.cf.1TRKcPyN9O.css

HTTP/1.1 200 OK

Content-Type: text/css

Connection: keep-alive

Keep-Alive: timeout=300

Server: nginx

Accept-Ranges: bytes

Age: 133

Via: 1.1 varnish

X-Cache: HIT

Date: Sat, 02 Apr 2016 21:01:14 GMT

Expires: Sun, 02 Apr 2017 21:01:14 GMT

Cache-Control: max-age=31536000

ETag: W/"0"

Last-Modified: Sat, 02 Apr 2016 21:01:14 GMT

X-Original-Content-Length: 22956

Vary: Accept-Encoding

Vary: Accept-Encoding

Content-Length: 22956

X-Page-Speed: 1.11.33.0-0

-Hans

Op donderdag 31 maart 2016 22:22:44 UTC+2 schreef Jeff Kaufman:

[Jeff Kaufman]

Sorry! Only half of this fix is in 1.11. Specifically,
https://github.com/pagespeed/ngx_pagespeed/commit/b081bb7 resolved
this for most users, but for some users we have unreleased changes on
master to clean up the rest of the duplication. That will be in 1.12
(if it's needed) or 2.0.