Long-standing upstream issues, resolved

The Apache Incubator trackers for mod_pagespeed and ngx_pagespeed are archived. Between them they still hold nearly 900 open issues (524 and 353 in October 2026), and an archived tracker cannot close any of them, so they stay open even after the problem is gone. We triaged every one of them from its title and report. We tied 61 of them to a specific change in the current code, the CHANGELOG or the release notes; two of those are marked likely, and one is resolved in part. The full list, with links, is on the new docs page Long-standing upstream issues resolved.

Some of them, briefly:

• Building ngx_pagespeed against a current nginx. Issues from 2016 to 2022 report compile failures with newer nginx, newer glibc, or as a dynamic module. Resolved in mod_pagespeed 1.1.0: the stock nginx of each supported distribution gets a prebuilt, signed module, so there is nothing to compile, and the released source builds against the nginx versions we support, listed under Which nginx version.
• ARM64. Reported in 2016 against ngx_pagespeed (“Supporting pagespeed on ARM devices?”); resolved in 1.1.0 with arm64/aarch64 builds for Apache and nginx on Linux.
• The archived Google package repository. Reported in 2020 and 2022 as GPG and “no longer signed” errors from apt; resolved by a maintained, signed repository, and since 2.5.0 apt-get install mod-pagespeed replaces the archived package in one step.
• A deadlock in shared-memory statistics. Reported in 2018: a hang that could block all server processes until a restart. Resolved in 2.2.0.
• Native lazy loading. Requested in 2019 against ngx_pagespeed, and in 2020 against mod_pagespeed by sites whose PageSpeed Insights report still flagged offscreen images. Resolved in 1.15.0+r18: lazyload_images can write loading="lazy" instead of swapping in a placeholder image.
• The file cache. Reports from 2016 to 2019 about the cache cleaner loading the disk, the cache growing past its limit and logs filling with lock-file errors. Resolved in 1.1.0, where Cyclone Cache, a fixed-size, memory-mapped cache with no cleanup passes, replaced the file cache.

The page links the rows to the CHANGELOG entry, the release notes or the source file that carries the change. We left out issues we could not tie to a specific change, and the rows we could not confirm against the reporter’s setup are marked “likely”. If one of the listed issues still happens to you on a current release, or you hit another one from those trackers, open an issue in We-Amp/mod_pagespeed with your version and a reproduction.