Skip to content

v1.0.8

Choose a tag to compare

@brianvarskonst brianvarskonst released this 26 Oct 18:12
· 29 commits to main since this release
v1.0.8

Nginx Cache 1.0.8 fixes three prewarm and keep-warm reliability problems. A page now counts as warmed only once Nginx could actually cache it, a failing sitemap no longer keeps already known pages cold, and a first keep-warm run that never finishes is no longer reported as healthy.

  • Prewarm success needs a complete response. An HTTP 200 whose body broke off or stalled after the headers used to be checkpointed as warmed, although Nginx stores no entry for an aborted transfer. The body is now streamed and discarded within the existing five-second limits, without buffering it in memory. An incomplete transfer is a retryable URL failure, and complete sibling URLs keep their progress.
  • Sitemap failures no longer block known targets. A sitemap error, such as an HTTP 503, used to stop the purge follow-up before any known page (for example the home page) was requested and before cache layer, remote and Cloudflare work ran. Known targets are now warmed in batches that do not spend the retry budget, and the remaining follow-up work runs. Discovery is retried with backoff after every failed attempt, also while a known page is still failing. A later successful discovery adds just the missing targets.
  • Precise discovery errors. Each failed sitemap is reported with its URL and a fixed reason: HTTP status, timeout, request failure, the 2 MiB budget, invalid XML, a non-sitemap document or forbidden XML declarations. Provider messages and response bodies are never stored. The latest failure appears as sitemap_discovery_failure in wp nginx-cache side-effects details and the diagnostic report until discovery succeeds again.
  • Overdue first keep-warm cycle. overdue used to require a completed cycle, so a first run that stalled, crashed on every attempt or never started kept Site Health at "good". The inactivity window now counts from the last completion, otherwise from the first cycle's start or first attempt, otherwise from its due cron event. Start-up, an event that is not yet due and a disabled keep-warm stay quiet, and a worker heartbeat does not replace a completed cycle.

On upgrade: option names, stored values and the generated Nginx configuration are unchanged, so no Nginx reload is required. Follow-up tasks queued by 1.0.7 continue unchanged. The sympress_nginx_cache_side_effects_processed payload additionally reports prewarm.discovery_complete. The new non-autoloaded diagnostic option sympress_nginx_cache_sitemap_discovery_failure is removed on uninstall.

Implementation:

Release preparation: #46

Release commit: f2f0c1c2bf810df628822590544ae09217b09675. The SSH-signed tag was verified locally with the SymPress release key.

Validation: all eight QA checks passed on each fix PR and on the release PR, each on its final rebased head, and the post-merge QA run on main passed. Local QA also passed: 113 tests / 566 assertions, coding standards, static analysis and hook checks. The WordPress 7.1.2 integration suites on MariaDB 11.8 passed with 314 assertions and 26 contention checks, plus 103 multisite checks. Every regression check was also confirmed to fail without its fix. The ZIP contains the production dependencies and passed checksum and source checks: 2,474 file checksums, 124 source files identical to the tag, and no development packages. Archive build and checks.

Download ns-nginx-cache-1.0.8.zip below for a ready-to-install WordPress package. The automatically generated GitHub source archives do not include the production dependencies. Composer users can update sympress/nginx-cache to ^1.0.8.

SHA-256 for ns-nginx-cache-1.0.8.zip:

3b03324f27c9d99cb64673d3730f86edd33a4eaf874358e8dea735bd1797c344