# HTTP Headers Reference

> Search 39 common HTTP request and response headers, from Accept to X-Frame-Options, with a plain description of what each one does.

- Page: https://mondaytool.com/tools/http-headers-reference
- Category: network-api
- Price: free, no sign-up. Most tools run in the browser, so input is not uploaded.
- Use it: open https://mondaytool.com/tools/http-headers-reference. It is an interactive web page; this file is its documentation.

Last updated: 16 October 2026

## Look up common HTTP headers

This **HTTP headers reference** lists 39 headers you meet most often when building or debugging web requests. Each entry shows the header name, whether it belongs to requests, responses or both, and a short description of its purpose.

## How to use it

1. Type a word into the search box, for example `cache`, `cors` or a header name such as `ETag`.
2. Use the tabs **All**, **Request**, **Response** or **Both** to narrow the list.
3. Read the description under each header name. The counter shows how many headers match.

## How it works

The list is built into the page, so searching is instant and needs no network call. Search checks the header name, the description and the type label. The Request and Response tabs also include headers marked **Both**, because those can appear in either direction. The Both tab shows only that group.

## What you see

| Field | Meaning |
| --- | --- |
| Name | The header as it is written on the wire, such as `Content-Type` |
| Type | Request, Response or Both |
| Description | What the header tells the client, server or cache |

The list covers content negotiation, caching, CORS, cookies, redirects, authentication, proxies and a few security headers such as `Content-Security-Policy` and `Strict-Transport-Security`.

## Assumptions and limits

- It is a short reference of common headers, not the full IANA registry.
- Descriptions are brief. They do not list every directive or syntax rule for a header.
- The tool does not send requests or read the headers of any live site.

## Frequently asked questions

### What is the difference between request and response headers?

Request headers are sent by the client, such as `Accept` or `Authorization`. Response headers come back from the server, such as `Set-Cookie` or `ETag`. Some, like `Cache-Control`, are used in both directions.

### Why do Both headers show under the Request tab?

A header marked Both can be sent in a request as well, so it is included when you filter by Request or Response.

### Can I see the headers a website actually returns?

Not here. This page only explains headers. Use your browser's network panel or an HTTP client to see real ones.
