CrawlCheck
Glossary · HTTP, edge and rendering

Edge redirect

A redirect generated by CDN or proxy configuration before the origin handles the request.

What Edge redirect does not show

Origin code inspection will not reveal it.

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.

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 · 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 Edge redirect

What is Edge redirect?

A redirect generated by CDN or proxy configuration before the origin handles the request.

What does Edge redirect not show or guarantee?

Origin code inspection will not reveal it.

Which area of the glossary does Edge redirect 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.

← Stale-while-revalidate  ·  Origin bypass →

See it in the full glossary · 731 terms across 19 areas.