Announcing mod_pagespeed binary release 1.9.32.3-stable

[Jeffrey Crowell]

Release 1.9.32.3-stable

The mod_pagespeed team is pleased to announce a new stable binary release, version 1.9.32.3. A list of the changes since the previous stable release (1.8.31.6) can be found below. This stable release is a clone of the 1.9.32.3-beta release.

Installation Instructions

If you are currently on the stable channel, you can update via the usual method.

If you installed the .rpm package, update with:

sudo yum update mod-pagespeed-stable
sudo /etc/init.d/httpd restart

If you installed the .deb package, update with:

sudo apt-get update
sudo apt-get upgrade
sudo /etc/init.d/apache2 restart

If you are currently on the beta channel and would like to switch to the stable channel, you must first uninstall mod_pagespeed and then install the stable package from: https://developers.google.com/speed/docs/mod_pagespeed/download

Instructions for building from source are available at: https://developers.google.com/speed/pagespeed/module/build_mod_pagespeed_from_source

New Features since 1.8.31.6

Enabled InPlaceResourceOptimization by default

In Place Resource Optimization is now enabled by default.

Improved PageSpeed admin site

Admin page improved to show more information, provide graphs, and perform cache-purging operations.

Purge individual URLs from cache

Allows cache entries to be purged by PageSpeed administrators.

Improved debug filter support

Many more filters now support debug logging, emitting explanatory comments inline when the debug filter is enabled.

"Sticky" Query Parameters

Set query parameters in cookies for persisting options across queries.

Signing resource URLs

Optionally cryptographically sign and verify resource URLs.

Restrict query params

Optionally restrict interpretation of query parameters, such as ?PageSpeedFilters or ?PageSpeedCssFlattenMaxBytes.

Issues Resolved since 1.8.31.6

• Issue 1028 Malformed CSS file can cause a hang in CSS parser.

• Issue 1025 Purge cache UI has problems in admin console.

• Issue 1012 JS error in rendered_image_dimensions filter when the same image appears multiple times on a page.

• Issue 1004 Disable SSLv3 and SSLv2 support in serf fetcher.

• Issue 992 Malformed CSS can lead to unbounded stack depth.

• Issue 989 IPRO with LoadFromFile on a resource that is already fully optimized serves cc:max-age=300.

• Issue 986 Default flattening limit is too low.

• Issue 985 Re-add query params when we get a redirection response.

• Issue 984 Fix handling of experiment spec, so that options are applied when using the default filters.

• Issue 982 Defer javascript not working in IE9 or IE11.

• Issue 978 Blacklist Windows Browser for transcoding to webp.

• Issue 969 Don't send inline WebP to Chrome/36 on iOS. See issue for workaround fix for both nginx and Apache.

• Issue 967 Don't relocate scoped style tags in prioritize_critical_css.

• Issue 965 Don't relocate scoped style tags.

• Issue 909 Strict mode detection is too conservative.

• Issue 853 Provide separate filters rewrite_javascript_external and rewrite_javascript_inline.

• Issue 850 dedup_inlined_images breaks site combined with lazyload_images and defer_javascript.

• Issue 813 Disable beaconing for bots.

• Issue 794 Colorize warnings and errors in message_history page.

• Issue 786 serf_url_async_fetcher.cc error messages using IP instead of domain name.

Jeff Crowell

mod_pagespeed team

Google