fix: ignore modern static-asset extensions#18
Merged
marcin-prerender merged 1 commit intoJun 12, 2026
Conversation
Add otf, webp, avif, and webmanifest to the static-asset ignore regex in the map $uri $prerender block of all three configs (nginx.conf, nginx-php/nginx.conf, nginx-reverse-proxy/nginx.conf), per the canonical list in prerender/integration-contract#1. Forwarding these asset requests to the rendering service surfaces crawler-visible 504s. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
OpsBeaconCharles
approved these changes
Jun 12, 2026
OpsBeaconCharles
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The bug
The
map $uri $prerenderstatic-asset ignore regex is missing modern asset extensions (otf,webp,avif,webmanifest). When a crawler requests one of these assets, the request is proxied to the Prerender rendering service, which rejects static assets with a 504 — so the crawler sees a 5xx on an asset that serves200for normal users.Live evidence
Verified against prerender.io's own site: Googlebot UA requesting
inter-*.woff2receives 504, while a normal UA receives 200. Any forwarded font/image request surfaces as a crawler-visible 5xx.Canonical reference
This propagates the canonical static-asset ignore list from prerender/integration-contract#1, which adds
.woff2 .otf .eot .webp .avif .webmanifest(woff2andeotwere already present here).Changes
Added
otf|webp|avif|webmanifestto the extension alternation in the identicalmap $uri $prerenderblock of all three configs:nginx.confnginx-php/nginx.confnginx-reverse-proxy/nginx.confCaveats
~*regex is case-insensitive and unanchored, soavialready incidentally coveredavif(anddoccoversdocx, etc.). The explicit entries match the canonical contract list; adding a$anchor would change matching behavior for URLs that merely contain these substrings, so it is deliberately out of scope for this PR. The flip side of staying unanchored is continued over-matching, e.g. a page URL like/blog/why-we-love-avifis treated as a static asset and never prerendered.mapblock).🤖 Generated with Claude Code