Retry-After
An HTTP response header that tells a client how long to wait before trying again, sent with a 429 (too many requests) or a 503 that will end. CrawlCheck sends it on every 429 it returns.
What Retry-After does not show
A well-behaved crawler waits that long; the header cannot make a badly behaved one wait, and a 503 without it reads as an outage of unknown length.
Definitions that name Retry-After
Related terms in HTTP, edge and rendering
The delivery layer between an origin and a client: proxies, caches, redirects, status codes and the headers that decide what a crawler actually received.
Link header · content negotiation · Markdown negotiation · Server-Timing · WWW-Authenticate · Allow header · Content-Digest · Origin server · Reverse proxy · CDN · Edge node · WAF · Bot score · TLS handshake · DNS resolution · DNS timeout · Connection timeout · Read timeout · Redirect chain · Redirect loop · 301 redirect · 302 redirect · 307 redirect · 308 redirect · 304 response · 404 response · 410 response · 429 response · 500 response · 502 response · 503 response · 504 response · HEAD request · GET request · Content type · MIME sniffing · Content encoding · Compression · Brotli · ETag · Last-Modified · If-None-Match · Cache hit · Cache miss · Cache key · Vary header · Stale response · Stale-while-revalidate · Edge redirect · Origin bypass · Response parity · Header parity · hreflang · canonical URL · HSTS · HSTS preload list · Content-Security-Policy · CSP nonce · edge cache · cache split · cache-buster · Cache-Control · Age header · render-blocking resource · payload text share · lazy loading · 404 and 410 status codes
Questions about Retry-After
What is Retry-After?
An HTTP response header that tells a client how long to wait before trying again, sent with a 429 (too many requests) or a 503 that will end. CrawlCheck sends it on every 429 it returns.
What does Retry-After not show or guarantee?
A well-behaved crawler waits that long; the header cannot make a badly behaved one wait, and a 503 without it reads as an outage of unknown length.
Which area of the glossary does Retry-After belong to?
HTTP, edge and rendering: The delivery layer between an origin and a client: proxies, caches, redirects, status codes and the headers that decide what a crawler actually received.
← Markdown negotiation · Server-Timing →
See it in the full glossary · 751 terms across 19 areas.