8cdf35929a
- rootFileTargets gives robots.txt, sitemap.xml and llms.txt their backend target also in state unknown without a last answer, so the failing fetch answers 503 with Retry-After: 60 instead of the app's 404 (L4 WR-08) - an older backend (absent) still passes through; sitemap files and verification files still need a site answer - expect-seo-down.txt expects the 503s and states the staging reason
18 lines
965 B
Plaintext
18 lines
965 B
Plaintext
# The CMS unreachable since the server started (NUXT_SEO_API_BASE on a
|
|
# closed port): pages render normally with their own head (fail open).
|
|
# robots.txt, sitemap.xml and llms.txt answer 503 with Retry-After, so a
|
|
# crawler retries: falling through to the app would serve a 404 that reads
|
|
# as an allow-all robots.txt, also on a staging site whose Disallow lives
|
|
# on the backend (L4 WR-08). With no site answer ever seen, sitemap files
|
|
# and verification files still fall through to the app as in v0.1.1.
|
|
200 /about contains=<title>Own about | Playground</title> notcontains=About us | Acme noheader=X-Robots-Tag count=application/ld+json:0
|
|
200 /plain contains=<title>Plain page | Playground</title>
|
|
503 /robots.txt header=Retry-After: 60
|
|
503 /sitemap.xml header=Retry-After: 60
|
|
503 /llms.txt header=Retry-After: 60
|
|
404 /sitemap-posts-1.xml
|
|
404 /google0123.html
|
|
# The HTML sitemap with the backend down is a 503 (never an empty page).
|
|
503 /mapa-strony
|
|
apicalls 0
|