Overview - Request headers (Content-Type, Accept)

What is it?

Request headers are pieces of information sent by a client to a server when making a web request. Two important headers are Content-Type and Accept. Content-Type tells the server what kind of data the client is sending. Accept tells the server what kind of data the client wants back.

Why it matters

Without these headers, servers and clients would not understand each other’s data formats. This would cause confusion, errors, or broken communication. For example, a server might send data in a format the client cannot read, or the client might send data the server cannot process. These headers make sure both sides speak the same language.

Where it fits

Before learning about request headers, you should understand basic HTTP requests and responses. After this, you can learn about other headers, authentication, and how APIs handle data formats and content negotiation.

Mental Model

Core Idea

Content-Type says what you are sending; Accept says what you want to receive.

Think of it like...

Imagine ordering food at a restaurant: Content-Type is like telling the chef what dish you are bringing to share, and Accept is like telling the waiter what kind of dish you want to eat.

┌───────────────┐       ┌───────────────┐
│   Client      │──────▶│   Server      │
│               │       │               │
│ Content-Type: │       │               │
│ "I send X"   │       │               │
│ Accept:       │       │               │
│ "I want Y"   │       │               │
└───────────────┘       └───────────────┘

Build-Up - 7 Steps

1

FoundationWhat are HTTP Request Headers

Concept: Introduce the idea of headers as extra information sent with web requests.

When your browser or app talks to a server, it sends a request. This request has a main part (like the URL) and extra details called headers. Headers tell the server things like who you are, what language you speak, or what kind of data you are sending.

Result

You understand that headers are key-value pairs sent with requests to give more context.

Knowing headers exist helps you see how web communication is more than just URLs and data; it includes important metadata.

2

FoundationUnderstanding Content-Type Header

3

IntermediateUnderstanding Accept Header

4

IntermediateCommon Content-Type and Accept Values

5

IntermediateContent-Type and Accept in API Requests

6

AdvancedContent Negotiation and Multiple Accept Types

7

ExpertPitfalls and Subtleties in Header Usage

Under the Hood

When a client sends a request, the HTTP protocol includes headers as text lines before the body. Content-Type header tells the server how to parse the body bytes into meaningful data structures. Accept header informs the server about the client's preferred response formats. The server uses this info to select the response Content-Type and encode data accordingly. This exchange happens in plain text over TCP/IP, and headers are parsed by HTTP libraries on both sides.

Why designed this way?

HTTP was designed to be flexible and extensible. Headers allow clients and servers to communicate metadata without changing the core protocol. Content-Type and Accept headers enable content negotiation, allowing diverse data formats to coexist. This design avoids hardcoding formats and supports evolving web standards.

Client Request ──────────────────────────────▶ Server
┌───────────────────────┐                     ┌───────────────────────┐
│ Headers:              │                     │ Parse Headers         │
│ Content-Type: X       │                     │ Determine how to read │
│ Accept: Y             │                     │ request body          │
│ Body (data in format X)│                     │ Choose response format│
└───────────────────────┘                     └───────────────────────┘
                                                │
                                                ▼
                                      Server Response with Content-Type Y

Myth Busters - 4 Common Misconceptions

Quick: Does Accept header control what the client sends or what it receives? Commit to your answer.

Common Belief:Accept header tells the server what data format the client is sending.

Tap to reveal reality

Quick: If Content-Type is missing, will the server always understand the data? Commit to your answer.

Common Belief:If Content-Type is missing, servers can always guess the data format correctly.

Tap to reveal reality

Quick: Can Accept header list multiple formats with priorities? Commit to your answer.

Common Belief:Accept header can only specify one format at a time.

Tap to reveal reality

Quick: Does the server always honor the Accept header exactly? Commit to your answer.

Common Belief:Servers always respond with the format requested in Accept header.

Tap to reveal reality

Expert Zone

1

Some APIs require exact Content-Type matches, while others accept compatible types like 'application/json; charset=utf-8'.

2

Quality values in Accept headers allow fine-grained control over response formats, but many clients omit them, losing negotiation power.

3

Certain proxies or middleware may strip or alter headers, causing unexpected behavior that is hard to debug.

When NOT to use

In simple static web pages or basic form submissions, setting Accept explicitly is often unnecessary. For binary data uploads, Content-Type must be precise, but Accept may be irrelevant. Alternatives include using URL parameters or custom headers for content negotiation when headers are insufficient.

Production Patterns

In real APIs, clients set Content-Type to 'application/json' for JSON payloads and Accept to the same to get JSON responses. Servers implement content negotiation to support multiple formats (JSON, XML, HTML). Logging and monitoring often track these headers to debug client-server mismatches. Some APIs use versioned media types in Content-Type and Accept for backward compatibility.

Connections

Content Negotiation

Content-Type and Accept headers are the core mechanism enabling content negotiation.

Understanding these headers is essential to grasp how clients and servers agree on data formats dynamically.

MIME Types

Content-Type and Accept headers use MIME types to specify data formats.

Knowing MIME types helps you correctly set and interpret these headers for diverse data types.

Human Language Translation

Like translators choosing languages to communicate, Content-Type and Accept headers help systems 'speak' compatible data languages.

This cross-domain view highlights the importance of clear communication protocols in any system.

Common Pitfalls

#1Sending JSON data without setting Content-Type header.

Wrong approach:POST /api/data HTTP/1.1 Host: example.com {"name":"Alice"}

Correct approach:POST /api/data HTTP/1.1 Host: example.com Content-Type: application/json {"name":"Alice"}

Root cause:Not realizing the server needs Content-Type to parse the JSON body correctly.

#2Setting Accept header to a format the server does not support.

Wrong approach:GET /api/info HTTP/1.1 Host: example.com Accept: application/xml

Correct approach:GET /api/info HTTP/1.1 Host: example.com Accept: application/json

Root cause:Assuming the server supports all formats without checking API documentation.

#3Using Accept header to specify what data is sent instead of what is expected in response.

Wrong approach:POST /api/data HTTP/1.1 Host: example.com Accept: application/json name=Alice

Correct approach:POST /api/data HTTP/1.1 Host: example.com Content-Type: application/x-www-form-urlencoded Accept: application/json name=Alice

Root cause:Confusing Accept with Content-Type roles in HTTP requests.

Key Takeaways

Content-Type header tells the server the format of data the client is sending.

Accept header tells the server the preferred format of the response data.

Both headers enable clear communication and prevent data format mismatches between client and server.

Content negotiation uses Accept header values to choose the best response format dynamically.

Missing or incorrect headers often cause subtle bugs and failed API calls.