1. Home
  2. Glossary
  3. HTTP header
Server/HTTP

HTTP header

A name and value pair sent along with a request or a response. Response headers carry the status of caching, compression, security rules and more.

Why it matters

Headers control caching, compression, security and indexing without changing the page itself, so many audit findings are fixed in server settings.

Example

HTTP/2 200
content-type: text/html; charset=utf-8
cache-control: max-age=3600

Where you will see it

The free HTTP header checker looks at this on a live page and explains what it finds in plain English: see status, redirects, every response header and timing, with plain-English notes.

Related terms

  • HTTP status code: The three-digit number a server returns with every response. 200 means success, 301 and 302 are redirects, 404 means not found and 503 means the service is temporarily unavailable.
  • Cache-Control: An HTTP response header that tells browsers and CDNs whether and for how long they may reuse a stored copy of a file.
  • Content-Security-Policy: An HTTP response header that lists which sources a page may load scripts, styles, images and other resources from.

Go deeper

  • HTTP headers explained: What HTTP response headers are, the ones that matter for caching, content, redirects, cookies, crawling and security, and how to view and read them.

← All 66 glossary terms

↑ ↓ to moveEnter to openEsc to closeAll results